[
https://issues.apache.org/jira/browse/SOLR-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099613#comment-13099613
]
Yonik Seeley edited comment on SOLR-2748 at 9/7/11 10:17 PM:
-------------------------------------------------------------
Hmmm, I'm not quite understanding the logic of this class.
CommitTracker.didCommit() (which is called by DUH2 after a commit finishes)
tries to cancel any pending scheduled operations and resets the doc counter to
0. But that seems like a bug since documents may have been added during the
commit, and a new commit may have been scheduled while the old commit was
executing. Of course we are going to lose track of that since run() sets
pending to null.
edit: and of course trying to cancel "pending" from the DUH2 like that is also
another race condition... which "pending" will it cancel? It could be the old
or the new, depending on the thread timings.
was (Author: [email protected]):
Hmmm, I'm not quite understanding the logic of this class.
CommitTracker.didCommit() (which is called by DUH2 after a commit finishes)
tries to cancel any pending scheduled operations and resets the doc counter to
0. But that seems like a bug since documents may have been added during the
commit, and a new commit may have been scheduled while the old commit was
executing. Of course we are going to lose track of that since run() sets
pending to null.
> 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: [email protected]
For additional commands, e-mail: [email protected]
