[jira] [Commented] (CASSANDRA-16561) Gossip is not populated with tokens/host_ids

["Brandon Williams (Jira)" <ji...@apache.org>]

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

Brandon Williams commented on CASSANDRA-16561:
----------------------------------------------

This will certainly affect scenarios where nodes don't already have this information, such after a complete cluster restart where some nodes are left down, and a new one attempts to bootstrap.  It will never have complete information about the ring for token selection.

> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org