David Capwell created CASSANDRA-19768:
-----------------------------------------
Summary: 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: Sam Tunnicliffe
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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
