[
https://issues.apache.org/jira/browse/SOLR-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker updated SOLR-7117:
--------------------------------
Attachment: SOLR-7117.patch
Patch which adds a property called "maxCoresPerNode". This value is respected
when finding nodes to host failed over replicas.
I am not happy with the "maxCoresPerNode" name but that seemed like the most
accurate name. "maxReplicasPerNode" might suggest this value does something
similar to "maxShardsPerNode" ?
I will add a test but wanted some feedback on the approach and the name for the
property.
> 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
>
>
> 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]
