-
Type:
Bug
-
Status: Resolved
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: Cluster/Gossip
-
Labels:None
-
Bug Category:Correctness - Consistency
-
Severity:Low
-
Complexity:Low Hanging Fruit
-
Discovered By:Code Inspection
-
Platform:All
-
Impacts:None
-
Since Version:
-
Source Control Link:
-
Test and Documentation Plan:
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