[
https://issues.apache.org/jira/browse/CASSANDRA-17805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583032#comment-17583032
]
Ekaterina Dimitrova commented on CASSANDRA-17805:
-------------------------------------------------
It seems this patch broke a large DTest which is ran on Jenkins but not in
CircleCI.
[https://ci-cassandra.apache.org/job/Cassandra-trunk/1270/testReport/dtest-large.replace_address_test/TestReplaceAddress/]
It fails consistently as per
[Butler|https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/replace_address_test/TestReplaceAddress/test_replace_active_node],
I am opening a follow up ticket if you can take a look. Thanks
> 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: [email protected]
For additional commands, e-mail: [email protected]
