[ https://issues.apache.org/jira/browse/CASSANDRA-16561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315384#comment-17315384 ]
Sam Tunnicliffe commented on CASSANDRA-16561: --------------------------------------------- As far as I remember (and I may be completely wrong), I'm not sure we've ever loaded persisted tokens/host id for other peers into gossip, only ever the states for the local instance. That was recently changed in CASSANDRA-16213 to address the case of a replacement after a full cluster bounce, but that only affects responses to shadow round requests. Otherwise I think it's always been the case that nodes learn those states only through the normal gossip mechanism. > Gossip is not populated with tokens/host_ids > -------------------------------------------- > > Key: CASSANDRA-16561 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16561 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Gossip > Reporter: Brandon Williams > Priority: Normal > Fix For: 2.2.x, 3.0.x, 3.11.x, 4.0.x > > > Originally when we began persisting host information such a tokens/host_id, > we would populate gossip with this information. At some point we began only > populating TokenMetadata, which gives us most of the same benefit, but in a > full ring restart where the gossip ether is empty, it populates useless info > such as : > {quote} > /10.101.32.212 > generation:0 > heartbeat:0 > TOKENS: not present > {quote} > which is the minimum required for a state to exist. Instead we should keep > gossip in sync with TMD when populating this information like we used to do. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org