[
https://issues.apache.org/jira/browse/SOLR-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14326858#comment-14326858
]
Mark Miller commented on SOLR-7117:
-----------------------------------
Hmm...don't we want to respect both collection max per node and the universal
max per node?
Since we respect the collection max on collection create and store it, I would
first argue we should probably keep it in consideration.
If we were to just stop respecting it and only the universal limit, we have to
consider the affect on back compat for a 5.1 upgrade.
> AutoAddReplicas should have a cluster wide property for controlling number of
> cores hosted on each node
> -------------------------------------------------------------------------------------------------------
>
> Key: SOLR-7117
> URL: https://issues.apache.org/jira/browse/SOLR-7117
> Project: Solr
> Issue Type: Improvement
> Reporter: Varun Thacker
> Priority: Minor
> Fix For: Trunk, 5.1
>
> Attachments: SOLR-7117.patch, SOLR-7117.patch
>
>
> Currently when finding the best node to host the failed replicas, we respect
> the maxShardsPerNode property. This is not an ideal solution as it's a per
> collection property and we need a cluster wide property. Also using
> maxShardsPerNode can lead to unequal distribution of replicas across nodes.
> We should just let users use the CLUSTERPROP API to set the max number of
> cores to be hosted on each node and use that value while picking the node the
> replica will be hosted on.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
