[
https://issues.apache.org/jira/browse/SOLR-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632587#comment-13632587
]
Shawn Heisey commented on SOLR-1488:
------------------------------------
My gut instinct on reading this was that allowing this could lead to an
alternate way of creating "huge tlog" problems ... someone might define only
idleTime and leave the others out. After a few minutes of thinking about it,
it's probably not any worse than the existing ways that people end up with huge
tlogs.
It seems to me that honoring both idleTime and maxTime would be the best way to
go. Using the example, if you have ten seconds of idle time, it should commit.
If you have a period of 30 seconds where each idle time never gets to 10
seconds, go ahead and commit. That would be harder to code, but the end result
would be better.
If this issue does get fixed, when I get around to making a 'huge tlog' wiki
page, I can include some advice about using maxDocs and/or maxTime in addition
to idleTime.
> autoCommit when idle
> --------------------
>
> Key: SOLR-1488
> URL: https://issues.apache.org/jira/browse/SOLR-1488
> Project: Solr
> Issue Type: Improvement
> Reporter: Matt Weber
> Priority: Minor
> Attachments: SOLR-1488.patch
>
>
> Enable autoCommit to execute after a given amount of idle time (no documents
> submitted).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
