cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "C. Scott Andreas (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-11688) Replace_address should sanity check prior node state before migrating tokens
Date Mon, 19 Nov 2018 02:32:01 GMT


C. Scott Andreas updated CASSANDRA-11688:
    Component/s: Streaming and Messaging

> Replace_address should sanity check prior node state before migrating tokens
> ----------------------------------------------------------------------------
>                 Key: CASSANDRA-11688
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Streaming and Messaging
>            Reporter: Jonathan Shook
>            Priority: Major
> During a node replacement, a replace_address was used which was associated with a different
node than the intended one. The result was that both nodes remained active after the node
came up. This caused several other issues which were difficult to diagnose, including invalid
gossip state, etc.
> Replace_address should be more robust in this scenario. It would be much more user friendly
if the replace_address logic would first do some basic sanity checks, possibly to include:
> - Pinging the other node to see if it is indeed “down”, if the address is different
than all local interface addresses
> - Checking gossip state of the node to verify that it is not known to peers.
> It may even be safest to require that both address reachability and gossip state are
required to show the replace_address as down by default before allowing any token migration
or other replace_address actions to occur.
> In the case that the replace_address is not ready to be replaced, the log should indicate
that you are trying to replace an active node, and cassandra should refuse to start.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message