[
https://issues.apache.org/jira/browse/CASSANDRA-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325170#comment-14325170
]
Richard Low commented on CASSANDRA-8336:
----------------------------------------
v3 works well and I was able to do a full cluster bounce with zero timeouts.
Here’s a few minor points:
* The shutting down node might as well set the version of the shutdown state to
Integer.MAX_VALUE since receiving nodes will blindly use that.
* Why does it increment the generation number? We call Gossiper.instance.start
with a new generation number set to the current time so it would make sense to
use that.
* If hit 'Unable to gossip with any seeds’ on replace, it shuts down the
gossiper. This throws an AssertionError in addLocalApplicationState since the
local epState is null.
> Quarantine nodes after receiving the gossip shutdown message
> ------------------------------------------------------------
>
> Key: CASSANDRA-8336
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8336
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Fix For: 2.0.13
>
> Attachments: 8336-v2.txt, 8336-v3.txt, 8336.txt
>
>
> In CASSANDRA-3936 we added a gossip shutdown announcement. The problem here
> is that this isn't sufficient; you can still get TOEs and have to wait on the
> FD to figure things out. This happens due to gossip propagation time and
> variance; if node X shuts down and sends the message to Y, but Z has a
> greater gossip version than Y for X and has not yet received the message, it
> can initiate gossip with Y and thus mark X alive again. I propose
> quarantining to solve this, however I feel it should be a -D parameter you
> have to specify, so as not to destroy current dev and test practices, since
> this will mean a node that shuts down will not be able to restart until the
> quarantine expires.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
