[
https://issues.apache.org/jira/browse/SOLR-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692117#comment-13692117
]
Shalin Shekhar Mangar commented on SOLR-4808:
---------------------------------------------
bq. I don't see a reason to have two parameters. It is quite confusing. We
should have only one property
There are two things that we want:
# Use ZK as the truth and assign nodes accordingly as and when they join the
cluster
# Increase/decrease replicas on-the-fly automatically using the replication
factor and maxShardsPerNode properties
While the former affects only those nodes that are joining the cluster, the
latter affects active and available nodes. It makes sense to have a switch to
disable #2.
> 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]
