On 2/21/2014 2:34 PM, Joshi, Shital wrote:
<updateHandler class="solr.DirectUpdateHandler2"> <updateLog> <str name="dir">${solr.ulog.dir:}</str> </updateLog><autoCommit> <maxTime>${solr.autoCommit.maxTime:600000}</maxTime> <maxDocs>100000</maxDocs> <openSearcher>true</openSearcher> </autoCommit> </updateHandler> Shouldn't we see DirectUpdateHandler2; start commit and DirectUpdateHandler2; end_commit_flush message in our log at least every ten minutes? I understand that if we have more than 100K documents to commit, hard commit could happen earlier than 10 minutes. But we see hard commit spaced out by more than 20 to 30 minutes and sometimes couple hours. Can you please explain this behavior?
The autoCommit will not happen if you haven't indexed anything since the last commit. As I understand it, the timer and document counter don't actually start until the moment you send an update request (add, update, or delete). If no updates have come in, they are turned off once the commit completes.
Are you seeing this happen when you do not have delays between updates? Thanks, Shawn
