[
https://issues.apache.org/jira/browse/SOLR-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16188793#comment-16188793
]
Varun Thacker commented on SOLR-11427:
--------------------------------------
Hi Erick,
Do you know the original motivation of "onlyIdDown" ?
While deleting a replica we need to specify collection,shard and replica . So
shouldn't the user know that he is deleting an active replica?
The scenario that you described totally happens . So to address that if we
didn't have "onlyIfDown" in the first place then the command would try to
delete the index , which would fail ( core is not present ) but atleast we
would cleanup the state - which is what the user wants at this point ?
> DELETEREPLICA with onlyIfDown specified should succeed if the host node is
> not present in the live_nodes Znode
> --------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-11427
> URL: https://issues.apache.org/jira/browse/SOLR-11427
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Erick Erickson
> Assignee: Erick Erickson
>
> The title says it pretty much, so opening up for discussion:
> Here's the problem. Let's say a node is killed via {{kill -9}}. The
> state.json file still says it's "active", but the node is gone from
> live_nodes. If the node in question never comes back, the replica's state
> doesn't necessarily get switched to "down", so specifying onlyIfDown fails
> with "node is active" message. This is all documented more thoroughly in
> SOLR-9361.
> The question is whether it's sufficient and/or safe to succeed in deleting
> the replica from state.json if the state is "active" _and_ the node is NOT
> present in live_nodes.
> I'm assigning to myself, but others should feel free to take it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
