[
https://issues.apache.org/jira/browse/CASSANDRA-16213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228747#comment-17228747
]
David Capwell commented on CASSANDRA-16213:
-------------------------------------------
Thanks for the feedback
bq. not required as endpoint states with heartbeat version -1 need not be sent
by examineGossiper
I think that was important for assassinate, so will try to look closer at your
patch and how it works with assassinate
bq. HostReplacementOfDowedClusterTest.hostReplacementOfDeadNode tests an
orderly shutdown, ... Can we maybe also test with an abrupt shutdown, that is
when the shutdown state is not broadcast and the node to be replaced is on
NORMAL state?
Makes a lot of sense, I can try working on this test (I assume I can just block
gossip messages as I can't kill -9 in jvm-dtest).
> Cannot replace_address /X because it doesn't exist in gossip
> ------------------------------------------------------------
>
> Key: CASSANDRA-16213
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16213
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip, Cluster/Membership
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.0-beta
>
>
> We see this exception around nodes crashing and trying to do a host
> replacement; this error appears to be correlated around multiple node
> failures.
> A simplified case to trigger this is the following
> *) Have a N node cluster
> *) Shutdown all N nodes
> *) Bring up N-1 nodes (at least 1 seed, else replace seed)
> *) Host replace the N-1th node -> this will fail with the above
> The reason this happens is that the N-1th node isn’t gossiping anymore, and
> the existing nodes do not have its details in gossip (but have the details in
> the peers table), so the host replacement fails as the node isn’t known in
> gossip.
> This affects all versions (tested 3.0 and trunk, assume 2.2 as well)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
