[
https://issues.apache.org/jira/browse/SOLR-8707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155341#comment-15155341
]
Hoss Man commented on SOLR-8707:
--------------------------------
bq. A long delay outside of configuration is a little worrying
sure ... with this type of approach, you'd want the "first trigger" to happen
at the initialDelay, and then repeat every autoCommitTime (as opposed to the
current logic which uses initialDelay == autoCommitTime)
it's also something that could be easily be added as a config option.
> Distribute (auto)commit requests evenly over time in multi shard/replica
> collections
> ------------------------------------------------------------------------------------
>
> Key: SOLR-8707
> URL: https://issues.apache.org/jira/browse/SOLR-8707
> Project: Solr
> Issue Type: Improvement
> Components: update
> Reporter: Michael Sun
>
> In current implementation, all Solr nodes start commit for all cores in a
> collection almost at the same time. As result, it creates a load spike in
> cluster at regular interval, particular when collection is on HDFS. The main
> reason is that all cores are created almost at the same time for a collection
> and do commit in a fixed interval afterwards.
> It's good to distribute the the commit load evenly to avoid load spike. It
> helps to improve performance and reliability in general.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
