lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Thacker (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-7117) AutoAddReplicas should have a cluster wide property for controlling number of cores hosted on each node
Date Fri, 20 Feb 2015 10:58:11 GMT

     [ 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

Updated patch.

Now we respect both "maxShardsPerNode" and "maxCoresPerNode". So if we hit any one of those
that node is not picked as a recovery node.



> 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, 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


Mime
View raw message