You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Davids (JIRA)" <ji...@apache.org> on 2015/10/01 04:44:04 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=14939199#comment-14939199 ] 

Steve Davids commented on SOLR-5748:
------------------------------------

Due to the continued comments about an impending "ZK as truth" switch for the 5.x branch, I went ahead and attempted to start using the Collection API and found it to be be a bit more burdensome than the classic mode. This particular ticket would go a long way to making the adding/removing replica process easy. I documented some of the annoyances in this thread: http://markmail.org/message/qungxgiab6njslpu

As for the previous comment: 
bq.  It would be good to have some kind of control over where the additional replicas will be so that the installation could decide that based on the disk space, memory availability etc.

That is now taken care of via SOLR-6220

> 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: Trunk
>
>
> 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.3.4#6332)

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