Hi Savvas, well, although it sounds strange: If a commit happens, a new Index Searcher is warming. If a new commit happens while a 'new' Index Searcher is warming, another Index Searcher is warming. So, at this point of time, you got 3 Index Searchers: The old one, the 'new' one and the newest one.
I don't know wheter the old one will be replaced by the new one until the newest one has finished warming, but it seems to be a good guess, since you can search while the new index is still committing. You should know that Lucene is built on a segment-architecture. This means every time you do a commit you write a completely new index-segment. Example: You got one segment in your index and a searcher for it, now you are committing. After the commit finished you got two segments for it and one searcher for both segments. Internally your indexSearcher consists of at least two segmentReaders. If you are committing three times at the same moment, you will warm 3 new SolrIndexSearchers that contain 3,4 and 5 segmentReaders. Your old SolrIndexSearcher contains 2 segmentReaders and is valid until the newer SolrIndexReader based on 3 segmentReaders is warmed. Regards, Em -- View this message in context: http://lucene.472066.n3.nabble.com/Concurrent-updates-commits-tp2459222p2459522.html Sent from the Solr - User mailing list archive at Nabble.com.
