lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-5748) Introduce autoManageReplicas collection property
Date Tue, 18 Mar 2014 17:07:47 GMT

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

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



bq. It would be good to have some kind of control over where the additional replicas 

where means? which node or where on the file system?

> 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.2#6252)

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


Mime
View raw message