You havne't given us a lot of information to go on (ie: full solrconfig.xml, log messages arround the tim of your update, etc...) but my best guess would be that you are seeing a delay between the time the new searcher is opened and the time the newSearcher is made available to requests due to cache warming.
the specifics of your cache configs and "newSearcher" event listeners would impact this ... and of course, you'd see log messages about opening hte searcher, the cache warming, etc.... : Date: Tue, 12 Aug 2014 07:18:20 -0700 (PDT) : From: cwhit <cwhi...@solinkcorp.com> : Reply-To: solr-user@lucene.apache.org : To: solr-user@lucene.apache.org : Subject: Updates to index not available immediately as index scales, : even with autoSoftCommit at 1 second : : I've been trying to debug through this but I'm stumped. I have a Solr index : with ~40 million documents indexed currently sitting idle. I update an : existing document through the web interface (collection1 -> Documents -> : /update) and the web request returns successfully. At this point, I expect : the document to be updated on future searches within 1 second, but that's : not the case. The document can sometimes not be updated to future searches : for several minutes. What could be causing this, and how can it be : remedied? : : Within my solrconfig.xml, I have the following commit properties set: : : <autoSoftCommit> : <maxTime>1000</maxTime> : </autoSoftCommit> : : <autoCommit> : <maxTime>300000</maxTime> : <openSearcher>false</openSearcher> : </autoCommit> : : Running an identical Solr configuration but with thousands of documents : (rather than tens of millions), the updates are available immediately. : : : : : -- : View this message in context: http://lucene.472066.n3.nabble.com/Updates-to-index-not-available-immediately-as-index-scales-even-with-autoSoftCommit-at-1-second-tp4152511.html : Sent from the Solr - User mailing list archive at Nabble.com. : -Hoss http://www.lucidworks.com/
