[ https://issues.apache.org/jira/browse/CASSANDRA-16213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249435#comment-17249435 ]
David Capwell commented on CASSANDRA-16213: ------------------------------------------- Thanks for the review [~paulo]. bq. I think it should be pretty safe to have this enabled by default For our environment, the plan is to default to true, so I am ok with this. Another option is to default this to false for now and after "some time" we change the default to true... the hard part is when "some time" is as this is super edge case-y (small number of times within a year). Ill leave this open for now, give time for [~samt] to comment as well. bq. or even remove this knob altogether I am a fan of feature flags, so rather keep it to revert back if there is ever seen a reason to. > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org