What version of Solr? If it's Solr 4.x, see: http://searchhub.org/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/
Let me say that your settings are _extremely_ aggressive. Hard committing every second is _very_ likely to cause you significant problems down the road so be careful here. but otherwise, the other two suggestions may help you out. I suspect that what's happening is that your autowarm times are exceeding the interval between when you commit and when you query, so the old searcher (that doesn't know about the new additions) is responding to the request. Best, Erick On Wed, Aug 13, 2014 at 5:48 AM, Dmitry Kan <solrexp...@gmail.com> wrote: > Hi, > > you can use: > > > - > > waitSearcher = "true" | "false" — default is true — block until a new > searcher is opened and registered as the main query searcher, making the > changes visible. > > on the commit request. > > Dmitry > > > > On Wed, Aug 13, 2014 at 3:06 PM, M, Arjun (NSN - IN/Bangalore) < > arju...@nsn.com> wrote: > > > Hi, > > > > I have a query regarding solr commits. We have a use case where > we > > immediately query solr db after committing. We found that some data is > > missing as part of query results. We are predicting that commit wouldn't > > have completed when we query the solr db. > > > > Our solr commit config as follows. > > > > <autoCommit> > > <maxDocs>100</maxDocs> > > <maxTime>1000</maxTime> > > <openSearcher>true</openSearcher> > > </autoCommit> > > > > I have below question: > > > > - Is there a way to ensure that commit is completed before we query > > the database or proceed with further commits? > > > > Any help here is highly appreciated.. > > > > > > Thanks & Regards, > > Arjun M > > > > > > > > > > > > > -- > Dmitry Kan > Blog: http://dmitrykan.blogspot.com > Twitter: http://twitter.com/dmitrykan > SemanticAnalyzer: www.semanticanalyzer.info >
