On 7/24/2013 3:33 AM, Furkan KAMACI wrote: > I am indexing and check the admin stats page. I see that: > > commits: 471 > > autocommit maxTime: 15000ms > > autocommits: 414 > > soft autocommits: 0 > > optimizes: 12 > > docsPending: 388 > > adds: 305 > > cumulative_adds: 2154245 > > cumulative_deletesByQuery: 14 > > cumulative_adds: 2154245 > > > My document count still same, it does not increase. What is that autocommit > for and why it does not auto commit at each 15 seconds? What does > cumulative_adds means doe it mean when commit is done 2154245 document will > be added?
An autocommit will happen 15 seconds after you first add a document. If you aren't adding any more documents, then there's no reason to do the autocommit, so Solr won't do it. This next part is speculation, I don't actually know whether this is how it works, it just makes sense to me: I believe that if your autoCommit configuration has openSearcher set to false, then the autocommit won't drop the values of docsPending and other stat fields to zero. Only a commit (or soft commit) with openSearcher set to true will do so, because a commit with openSearcher=false just flushes the data to disk, it doesn't make it available for searching. The cumulative entries are historical values -- the number of documents that have been added or deleted and the number of errors encountered over the entire life of the update handler - typically as long as this instance of Solr has been running. Just an FYI - 15 seconds is a VERY short time to do an autocommit with openSearcher set to false. If you are doing this with openSearcher set to true, then it would be better for you to do this with autoSoftCommit and do the autoCommit on a longer interval with openSearcher=false. Thanks, Shawn
