I would take the server log for those 10 seconds (plus buffer) and really
try to see if something happens in that period.
I am thinking an unexpected commit, index large, alias switch. That may
help you to narrow down the kind of error.
Another option is whether you got empty result or a connection error. I am
thinking firewall that held on but then dropped a connection.
Both of these are unlikely but since you seem to be stuck....
Regards,
Alex
On Thu, Aug 15, 2019, 6:02 PM Brian Lininger, <brian.linin...@veeva.com>
wrote:
> Hi All,
> I'm seeing some odd behavior that I'm hoping someone might have encountered
> before. We're using Solr 6.6.6 and very infrequently (happened twice in
> the past year) we're getting 0 hits returned for a query that I know should
> have results. We've hit this issue once over the past year in 2 separate
> collections (both with a single shard), each with several million
> documents, where a query will return 0 hits. I see a similar query run
> 5-10s later and it will get the expected # of hits (~1M hits) so I know
> that we haven't reindexed a million docs between the two queries. Besides
> that I can see that between the 2 queries we only added 150-200 docs with a
> single commit so I don't see how that could affect the results in this
> manner.
>
> We have a moderate indexing load during the time we see this, we seen much
> higher indexing loads without issue but it's also not idle either. I've
> spent a bunch of time trying to reproduce this, tinkering with queries
> because I assumed that the problem had to be with the search query and not
> with Solr. Search times for both queries (those with 0 hits and those with
> 10k+ hits) are taking 30-40ms.
>
> Anyone run into something like this? Any ideas on something to look for?
>
> Thanks,
> Brian Lininger
>
