[
https://issues.apache.org/jira/browse/SOLR-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134963#comment-14134963
]
Shalin Shekhar Mangar commented on SOLR-6482:
---------------------------------------------
I'm a little confused about this feature. You say that deleting index
automatically is scary and then you talk about ZK as truth and about replicas
coming back up. What is the use-case behind onlyIfDown? Why would anyone invoke
DELETEREPLICA against a replica if they don't want it to be removed from
cluster state?
> 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
> Attachments: 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: [email protected]
For additional commands, e-mail: [email protected]
