You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (Jira)" <ji...@apache.org> on 2024/07/30 06:59:00 UTC

[jira] [Commented] (CASSANDRA-19768) nodetool assassinate of a CMS voting member should be allowed and should remove it from the CMS group

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

Marcus Eriksson commented on CASSANDRA-19768:
---------------------------------------------

PR that removes the assassinated node from the cms before doing the operation

Should note that {{nodetool assassinate}} is now mostly included for API compatibility with earlier versions - an operator should always be able to use {{nodetool removenode}} in real clusters now.

> nodetool assassinate of a CMS voting member should be allowed and should remove it from the CMS group
> -----------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-19768
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19768
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Transactional Cluster Metadata
>            Reporter: David Capwell
>            Assignee: Marcus Eriksson
>            Priority: Normal
>             Fix For: 5.x
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> nodetool assassinate is a dangerous command but is needed when the node to be removed really can’t be accessed anymore (such as host failures).  But when the node to be removed is a member of CMS, we block this action with the following error
> {code}
> Can not commit transformation: "INVALID"(Rejecting this plan as the node NodeId{id=3} is still a part of CMS.).
> {code}
> If the node in question is not up, and we call nodetool assassinate, we should then try to remove that node from the CMS membership group
> Steps to repo
> * Start 4 node cluster
> * nodetool cms reconfigure 3
> * targetNode = <one of the nodes in CMS>
> * stop targetNode
> * nodetool assassinate targetNode



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org