bq: Hi - i sometimes see the too many searcher warning to since some 5.x version. The warning cloud has no autoCommit and there is only a single process ever sending a commit, only once every 10-15 minutes orso
This is very surprising unless your autowarming is taking 10-15 minutes, almost assuredly impossible given your description. So my theory is that "something" is sending commits far more often than you think. I'd take a look at the Solr logs, you should see messages when commits happen. The logs should also tell you how long autowarming takes. For that matter so will the plugins/state page. Something's definitely fishy, I cannot reconcile you getting occasional messages about too many searchers and that rare a commit. On Wed, Nov 18, 2015 at 3:11 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 11/17/2015 1:11 AM, adfel70 >> >> Could it be that the parameter waitSearcher=true doesn't really work? >> or maybe I don't understand something here... > > > I am just guessing with this, but I think this is likely how it works: > > I believe that if maxWarmingSearchers is exceeded, a commit call will return > more quickly than usual, and Solr will not attempt to open a new searcher > with that commit, because the threshold has been exceeded. > > Basically, when there are too many searchers warming at once, new ones > cannot be created, which means that Solr cannot make the visibility > guarantees it usually makes. > > CloudSolrServer should be identical in function to CloudSolrClient, I don't > think you have to worry about it being deprecated for right now. You'll > want to switch before 6.0. > > Thanks, > Shawn >
