[
https://issues.apache.org/jira/browse/CASSANDRA-17805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-17805:
--------------------------------------
Fix Version/s: 4.2
(was: 4.x)
Since Version: 2.0.0
Source Control Link:
https://github.com/apache/cassandra/commit/05eb476c498d64dcfdb6542da64b789195c9a6d7
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> 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.2
>
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
