You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2016/05/05 19:58:12 UTC
[jira] [Commented] (SOLR-7117) AutoAddReplicas should have a
cluster wide property for controlling number of cores hosted on each node
[ https://issues.apache.org/jira/browse/SOLR-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272960#comment-15272960 ]
Mark Miller commented on SOLR-7117:
-----------------------------------
Hey [~varunthacker], think we can commit this?
> 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
> Assignee: Varun Thacker
> Priority: Minor
> Fix For: 5.2, master
>
> Attachments: SOLR-7117.patch, 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org