[
https://issues.apache.org/jira/browse/CASSANDRA-17805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579798#comment-17579798
]
David Capwell commented on CASSANDRA-17805:
-------------------------------------------
Starting commit
CI Results (pending):
||Branch||Source||Circle CI||Jenkins||
|trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17805-trunk-D8B2B58B-977F-4DDF-8BE1-31BE0B7356F0]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17805-trunk-D8B2B58B-977F-4DDF-8BE1-31BE0B7356F0]|[build|unknown]|
> When doing a host replacement, we need to check that the node is a live node
> before failing with "Cannot replace a live node..."
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17805
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17805
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Bootstrap and Decommission
> Reporter: Francisco Guerrero
> Assignee: Francisco Guerrero
> Priority: Normal
> Fix For: 4.x
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently, during a node replacement, we check that the node has not updated
> gossip for a configured {{ring_delay}} amount of time (defaults to 30
> seconds). If we see an update from the node that we are replacing in less
> than the configured time, we throw a {{UnsupportedOperationException}} with
> message {{Cannot replace a live node...}}. However, we never check whether
> the node is reporting as alive or not alive.
> We need an additional check to ensure that the node being replaced is
> reported as live; and only then throw the {{UnsupportedOperationException}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
