[
https://issues.apache.org/jira/browse/SOLR-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906829#comment-13906829
]
Shalin Shekhar Mangar commented on SOLR-5748:
---------------------------------------------
bq. Something that also decreases replicas makes more sense to me
The idea was suggested by Yonik in an earlier discussion. See
https://issues.apache.org/jira/browse/SOLR-4808?focusedCommentId=13692130&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13692130
We can have just one property, say 'autoManageReplicas' which can be used for
both creating as well as destroying replicas as long as replicationFactor is
configurable per-shard. Otherwise there are use-cases where separating the two
properties would make sense.
I'm going to rename this issue and the property to autoManageReplicas.
> Introduce autoIncreaseReplicas collection property
> --------------------------------------------------
>
> Key: SOLR-5748
> URL: https://issues.apache.org/jira/browse/SOLR-5748
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Fix For: 5.0
>
>
> I propose to introduce a collection property called autoIncreaseReplicas.
> This will be used only with the ZK as truth mode. If set to true, then
> whenever the number of replicas for a shard fall below the replicationFactor
> and the down nodes do not come back up for a configurable amount of time,
> additional replicas will be started up automatically.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
