If you see "WARNING: too many searchers on deck" or something like that in the logs, that could cause this behavior and would indicate you are opening searchers faster than Solr can keep up.
- Mark On Tue, Nov 17, 2015 at 2:05 PM Erick Erickson <erickerick...@gmail.com> wrote: > That's what was behind my earlier comment about perhaps > the call is timing out, thus the commit call is returning > _before_ the actual searcher is opened. But the call > coming back is not a return from commit, but from Jetty > even though the commit hasn't really returned. > > Just a guess however. > > Best, > Erick > > On Tue, Nov 17, 2015 at 12:11 AM, adfel70 <adfe...@gmail.com> wrote: > > Thanks Eric, > > I'll try to play with the autowarm config. > > > > But I have a more direct question - why does the commit return without > > waiting till the searchers are fully refreshed? > > > > Could it be that the parameter waitSearcher=true doesn't really work? > > or maybe I don't understand something here... > > > > Thanks, > > > > > > > > > > -- > > View this message in context: > http://lucene.472066.n3.nabble.com/CloudSolrCloud-Commit-returns-but-not-all-data-is-visible-occasionally-tp4240368p4240518.html > > Sent from the Solr - User mailing list archive at Nabble.com. > -- - Mark about.me/markrmiller
