[
https://issues.apache.org/jira/browse/SOLR-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690322#comment-13690322
]
Yonik Seeley commented on SOLR-4808:
------------------------------------
bq. We need to redefine replicationFactor
replicationFactor has always been the "target". The property does not fully
define how that target is generally met, and
it doesn't not mean that if the target isn't exactly met that the cluster is
invalid somehow.
bq. 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.
Agreed - if it's explicit, we should allow it. I'm not sure I see the problem
here.
> 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]
