[
https://issues.apache.org/jira/browse/SOLR-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690216#comment-13690216
]
Noble Paul commented on SOLR-4808:
----------------------------------
We need to redefine replicationFactor as the minimum no:of replicas for a given
shard. The cluster will have atleast those many no:of replicas for that given
shard. If the number falls below , that the overseer should attempt to bring
the number upto that.
What if a node is asked to join a shard which has enough replicas according to
the replicationFactor? It should be allowed to do so but the replicationFactor
should remain same till it is changed through the cluster admin command.
replicationFactor value must be persisted per shard . We should be able to
manipulate the value
* per shard : relevant for custom sharding
* entire cluster : for hash based setup the user would just update it cluster
wide
* shard.keys values : for composite id collections it make sense to change the
value by providing just the keys and the command can identify the appropriate
shards
> Persist and use replication factor at Collection and Shard level
> ----------------------------------------------------------------
>
> Key: SOLR-4808
> URL: https://issues.apache.org/jira/browse/SOLR-4808
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Anshum Gupta
> Assignee: Shalin Shekhar Mangar
> Labels: solrcloud
>
> The replication factor for a collection as of now is not persisted and used
> while adding replicas.
> We should save the replication factor at collection factor as well as shard
> level.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
