We've seen this a few times now and trying to determine exactly what is going on.
Today, while a crawl was occurring we tried to perform a search. The user initially got over 100 hits. Then when going to the next page, the hit count changed to 0.
After the crawl complete the hit count is still 0 and we are confident that result is wrong.
Also, when clicking Browse, the user no longer sees the Groups that she should be seeing. The display is only showing the public results. It's behaving exactly as if she logged out, or if her ACL information is not showing her the results she should see.
When this has happened in the past it seems to have magically corrected itself within a few hours.
We're still running 10.1.8 and preparing to upgrade to the latest. Most of our crawls are NTFS. Is this a known issue that's been fixed? Is there anything I can do to fix this?
Obvious questions are:
Was the crawler completely finished and not just done fetching?
Was the index optimizer running at this time? This could definitely lead to these strange results.
Behavior definitely sounds like user was not logged in. I assume you saw the user ID in the top right of search indicating you are logged in?
We are running 126.96.36.199.0 and don't have those issues.
I've actually submitted an SR for this.
But yes, the crawl was complete. At least according to the Schedules page on the admin site. And no, I was not rebuilding the index at that time. I have that set to go only on Sunday afternoons.
We changed this setting:
SES Admin UI->Global Settings->Query Configuration->Security Filter Lifespan (minitue) = 0
And it may have helped. Still not entirely sure since the problem is intermittent and we have not been able to determine a cause.