[
https://issues.apache.org/jira/browse/SOLR-8707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155264#comment-15155264
]
Mark Miller commented on SOLR-8707:
-----------------------------------
A long delay outside of configuration is a little worrying to me because some
people will restart a cluster while doing full indexing (message service or
something). If you basically ignore the first autocommit, you can drastically
raise the tlog ram reqs I think. Just something to consider.
> 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]
