[
https://issues.apache.org/jira/browse/CASSANDRA-16561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315576#comment-17315576
]
Sam Tunnicliffe commented on CASSANDRA-16561:
---------------------------------------------
I agree, I don't think there's anything wrong with populating the
tokens/host_id, I've always assumed there was a reason and that I wasn't aware
of it. I'm not sure I follow why this option would still present a problem in
the "bootstrap after full cluster restart with some nodes kept down" scenario
though? The ring view should be accurate in that case, unless you're thinking
of a situation where a movement occurred prior to the bounce and only the
still-down nodes witnessed it?
> 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
