cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Jira)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-16146) Node state incorrectly set to NORMAL after nodetool disablegossip and enablegossip during bootstrap
Date Tue, 29 Sep 2020 15:55:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-16146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204050#comment-17204050
] 

Brandon Williams commented on CASSANDRA-16146:
----------------------------------------------

Indeed, that looks related to CASSANDRA-16127.

> 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
>             Fix For: 3.0.x, 3.11.x, 4.0-beta3
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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


Mime
View raw message