You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Jira)" <ji...@apache.org> on 2020/09/28 17:28:00 UTC
[jira] [Commented] (CASSANDRA-16146) Node state incorrectly set to
NORMAL after nodetool disablegossip and enablegossip during bootstrap
[ https://issues.apache.org/jira/browse/CASSANDRA-16146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203409#comment-17203409 ]
Brandon Williams commented on CASSANDRA-16146:
----------------------------------------------
bq. Operator runs nodetool to stop and re-start gossip. The gossip state gets flipped to NORMAL
We should perhaps just not allow this outside of NORMAL, since in that case you probably want to just stop the the node instead.
> Node state incorrectly set to NORMAL after nodetool disablegossip and enablegossip during bootstrap
> ---------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-16146
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16146
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
> Reporter: Yifan Cai
> Assignee: Yifan Cai
> Priority: Normal
>
> At high level, {{StorageService#setGossipTokens}} set the gossip state to {{NORMAL}} blindly. Therefore, re-enabling gossip (stop and start gossip) overrides the actual gossip state.
>
> It could happen in the below scenario.
> # Bootstrap failed. The gossip state remains in {{BOOT}} / {{JOINING}} and code execution exits StorageService#initServer.
> # Operator runs nodetool to stop and re-start gossip. The gossip state gets flipped to {{NORMAL}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org