[
http://issues.apache.org/jira/browse/SOLR-65?page=comments#action_12447104 ]
Hoss Man commented on SOLR-65:
------------------------------
Thining about this purely from a configuration standpoint, without any regard
to implimentation complexity, the most general pupose options i can think of
would be:
commitFrequencyHardMin (milliseconds)
commitFrequencySoftMin (milliseconds greater then commitFrequencyHardMin)
commitFrequencyTestDelay (milliseconds)
commitFrequencySoftMax (milliseconds greater then commitFrequencySoftMin)
commitFrequencyHardMax (milliseconds greater then commitFrequencySoftMax)
autoCommitDocs (integer)
...assuming timeSinceLastCommit, timeSinceLastAddOrDelete, and
numDocsAddedSinceLastCommit are available to is, these are the situations in
which a commit would happen...
a) commitFrequencyHardMax <= timeSinceLastCommit
b) commitFrequencySoftMax <= timeSinceLastCommit < commitFrequencyHardMax
&& commitFrequencyTestDelay <= timeSinceLastAddOrDelete
c) commitFrequencySoftMin <= timeSinceLastCommit < commitFrequencySoftMax
&& [commit command recieved]
d) commitFrequencyHardMin <= timeSinceLastCommit < commitFrequencySoftMin
&& commitFrequencyTestDelay <= timeSinceLastAddOrDelete
&& [commit command recieved]
The situation where autoCommitDocs <= numDocsAddedSinceLastCommit would be
generate a commit command (just as if a user had issued it)
I *think* that various usages of those params (assuming they could be modified
on the lfy using JMX or some new command) would cover all of the use cases
yonik described, as well as all the ones i can think of.
(implimenting that may be overkill however)
> autoCommit/autoOptimize implementation + multithreaded document adding
> ----------------------------------------------------------------------
>
> Key: SOLR-65
> URL: http://issues.apache.org/jira/browse/SOLR-65
> Project: Solr
> Issue Type: New Feature
> Components: update
> Reporter: Mike Klaas
> Assigned To: Mike Klaas
> Attachments: autocommit_patch.diff
>
>
> Basic implementation of autoCommit/autoOptimize functionality, plus overhaul
> of DUH2 threading to reduce contention
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
