[
https://issues.apache.org/jira/browse/SOLR-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374914#comment-15374914
]
Noble Paul commented on SOLR-7280:
----------------------------------
The sorting of shards to be loaded in the following order
# The shards with least no:of replicas in *down* nodes and there is at least
one live node waiting for replicas of this shard. If these nodes are in *down*
nodes, it is no use bringing up a replica because, until those *down* nodes
come up, that shard cannot be up
# The shards with max no:of replica in *live* nodes. Because more replicas in
other nodes are waiting for this replica to be up
# least no:of replicas in my node. This helps us finish a shard by starting the
least no:of cores
# finally, use the replica name to break the tie (this does not matter, but
helps in having a predictable order)
> Load cores in sorted order and tweak coreLoadThread counts to improve cluster
> stability on restarts
> ---------------------------------------------------------------------------------------------------
>
> Key: SOLR-7280
> URL: https://issues.apache.org/jira/browse/SOLR-7280
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Noble Paul
> Fix For: 5.2, 6.0
>
> Attachments: SOLR-7280.patch, SOLR-7280.patch
>
>
> In SOLR-7191, Damien mentioned that by loading solr cores in a sorted order
> and tweaking some of the coreLoadThread counts, he was able to improve the
> stability of a cluster with thousands of collections. We should explore some
> of these changes and fold them into Solr.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
