[
https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15213679#comment-15213679
]
Ramkumar Aiyengar commented on SOLR-6359:
-----------------------------------------
Yeah, you are right that you get better control by tweaking one vs the other.
With num logs, you can get an approximation to amount of time for which you
keep logs (ie number of commits).. I agree that's not exact, and it would be
good to have the time itself as a config option.
.
The other option is to leave the num logs at unlimited, and tweak the number of
records, which probably helps to protect against going berserk with log sizes
if your indexing rates vary wildly. We do this in our setups, ie leave the
number of files unlimited, while set the records to keep..
> Allow customization of the number of records and logs kept by UpdateLog
> -----------------------------------------------------------------------
>
> Key: SOLR-6359
> URL: https://issues.apache.org/jira/browse/SOLR-6359
> Project: Solr
> Issue Type: Improvement
> Reporter: Ramkumar Aiyengar
> Assignee: Ramkumar Aiyengar
> Priority: Minor
> Fix For: 5.1, master
>
> Attachments: SOLR-6359.patch
>
>
> Currently {{UpdateLog}} hardcodes the number of logs and records it keeps,
> and the hardcoded numbers (100 records, 10 logs) can be quite low (esp. the
> records) in an heavily indexing setup, leading to full recovery even if Solr
> was just stopped and restarted.
> These values should be customizable (even if only present as expert options).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
