You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2014/09/17 16:58:35 UTC
[jira] [Resolved] (SOLR-6482) Add an onlyIfDown flag for
DELETEREPLICA collections API command
[ https://issues.apache.org/jira/browse/SOLR-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erick Erickson resolved SOLR-6482.
----------------------------------
Resolution: Fixed
Fix Version/s: 5.0
4.11
Incorporates the forgotten test too
> Add an onlyIfDown flag for DELETEREPLICA collections API command
> ----------------------------------------------------------------
>
> Key: SOLR-6482
> URL: https://issues.apache.org/jira/browse/SOLR-6482
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Affects Versions: 4.11, 5.0
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Minor
> Fix For: 4.11, 5.0
>
> Attachments: SOLR-6482-test.patch, SOLR-6482.patch, SOLR-6482.patch, SOLR-6482.patch
>
>
> Having the DELETEREPLICA delete the index is scary for some situations, especially ones in which the operations people are taking more explicit control of the topology of their cluster. As we move towards ZK being the "one source of truth" and deleting replicas that then come back up, this is even scarier.
> I propose to have an optional flag onlyIfDown that remove the replica from the ZK cluster state if (and only if) the node was offline. Default value: false.
--
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