It's just a single query that results in 0 hits, I had the same thought of
just adding code to retry the query when we get 0 hits (assuming that we
expect there to be hits). That's likely going to be the interim solution
so that we can get more info when this occurs. It's hard to triage when
it's
is there several 0 results in a row as an anomaly. Or really just one?
You could nearly add SolrJ code to rerun 0-result query with full debug on
if it is a rare enough event.
Regards,
Alex
On Fri, Aug 16, 2019, 12:05 PM Brian Lininger,
wrote:
> Yeah, I thought of those same problems at f
Yeah, I thought of those same problems at first and expected to find
something but no luck.
There are no errors in the solr log for the hour before/after the time that
we saw the issue, the only warnings I see are "PERFORMANCE WARNING:
Overlapping onDeckSearchers=2" but these are for other Collecti
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 connecti
Hi,
Did you encounter any error message during those occasions where you get 0
hits returned?
Regards,
Edwin
On Fri, 16 Aug 2019 at 06:02, Brian Lininger
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 in
