You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yifan Cai (Jira)" <ji...@apache.org> on 2020/09/28 17:25:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Yifan Cai updated CASSANDRA-16146:
----------------------------------
Bug Category: Parent values: Correctness(12982)Level 1 values: Consistency(12989)
Complexity: Low Hanging Fruit
Discovered By: Code Inspection
Severity: Low
Status: Open (was: Triage Needed)
> 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.}}
>
> {color:#24292e}It could happen in the below scenario.{color}
> {color:#24292e} {color} # 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