Solution 2 (downgrade to 7.5) fixes the problem by reverting to
building proximity (SpanNear) queries that do not explode
exponentially like MultiPhraseQuery does; but note that
SpanNearQueries in 7.5 are dropped (SOLR-12243), so they have
literally no effect whatsoever (aside from the minimal cost
Michael,
Thank you so much, that was extremely helpful. My googlefu wasn't good
enough I guess.
1. Was my initial fix just to stop it from exploding.
2. Will be the perm solutions for now until we can get some things squared
away for 8.0.
Sounds like even in 8 there is a problem with any graph
This is related to this issue:
https://issues.apache.org/jira/browse/SOLR-13336
Also tangentially relevant:
https://issues.apache.org/jira/browse/LUCENE-8531
https://issues.apache.org/jira/browse/SOLR-12243
I think your options include:
1. setting slop=0, which restores SpanNearQuery as the graph
Hello All,
We recently upgraded from Solr 6.6 to Solr 7.7.2 and recently had spikes in
memory that eventually caused either an OOM or almost 100% utilization of
the available memory. After trying a few things, increasing the JVM heap,
making sure docValues were set for all Sort, facet fields (thou
