[
https://issues.apache.org/jira/browse/SOLR-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099598#comment-13099598
]
Yonik Seeley commented on SOLR-2748:
------------------------------------
So I think the culprit might be CommitTracker.run()
At the end (after doing the commit) it has this code:
{code}
// check if docs have been submitted since the commit started
if (lastAddedTime > started) {
if (docsUpperBound > 0 && docsSinceCommit.get() > docsUpperBound) {
pending = scheduler.schedule(this, 100, TimeUnit.MILLISECONDS);
} else if (timeUpperBound > 0) {
pending = scheduler.schedule(this, timeUpperBound,
TimeUnit.MILLISECONDS);
}
}
{code}
Which seems to blindly schedule another commit (which should have already been
scheduled?). So now we have 2 commits scheduled for the next round, where
there should have only been one. It seems like those two commits now have the
potential to turn into 4 for the next round, and so on.
> autocommit commits too many times
> ---------------------------------
>
> Key: SOLR-2748
> URL: https://issues.apache.org/jira/browse/SOLR-2748
> Project: Solr
> Issue Type: Bug
> Reporter: Yonik Seeley
>
> autocommit seems to commit more frequently than configured.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
