[
https://issues.apache.org/jira/browse/SOLR-11989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-11989:
------------------------------
Issue Type: New Feature (was: Sub-task)
Parent: (was: SOLR-9735)
> Make it possible to place a replica of a collection on all nodes satisfying a
> given property
> --------------------------------------------------------------------------------------------
>
> Key: SOLR-11989
> URL: https://issues.apache.org/jira/browse/SOLR-11989
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling, SolrCloud
> Reporter: Shalin Shekhar Mangar
> Priority: Major
> Fix For: 7.4, master (8.0)
>
>
> Today replicas are placed according to policy rules but there is no way to
> drive the number of replicas based on policy e.g.
> Example 1: Put a replica of each shard of collection A on each node in the
> cluster
> {code}
> {"replica":">0", "node", "#ANY", "shard" : "#EACH", "collection" : "A"}
> {code}
> Example 2: Put a replica of each shard of collection A on every nodes with
> sysprop.region=east
> {code}
> {"replica":">0", "sysprop.region", "east", "shard" : "#EACH", "collection" :
> "A"}
> {code}
> The above two rules can be used to compute the replication factor of
> collection A but today the replicationFactor parameter passed in
> collection/shard creation neither takes the rule into account nor does it
> prevent conflicts. In fact, the replicationFactor should be omitted while
> creating collection A if the above rules are present.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
