You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2014/02/20 17:59:22 UTC

[jira] [Commented] (SOLR-5748) Introduce autoManageReplicas collection property

    [ https://issues.apache.org/jira/browse/SOLR-5748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907177#comment-13907177 ] 

Noble Paul commented on SOLR-5748:
----------------------------------

It is OK to prevent new replicas from coming up but it should not kill a replica if someone decreased the replicationFactor with modifyCollection API

> Introduce autoManageReplicas 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 autoManageReplicas. 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. Similarly, if the actual number of replicas is equal to or greater than replicationFactor then if old (previously down) nodes come back up then they will not be allowed to join the shard and will be unloaded instead.
> I think we should not unload running shards if number of replicas are more for now. We can change that later if needed.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org