[
https://issues.apache.org/jira/browse/CASSANDRA-16561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322440#comment-17322440
]
Sam Tunnicliffe commented on CASSANDRA-16561:
---------------------------------------------
{quote}we never send them in the shadow round
{quote}
In trunk, we do include the persisted state in a shadow round response if
that's all the state we have.
We also don't init that with ({{0, 0}}) any more, but with a special value that
indicates it represents persisted, not learned state.
This all changed in CASSANDRA-16213 to help the case of replacing a down node
(possibly following a full cluster bounce) and there are comments in
{{SS::prepareForReplacement}} and {{Gossiper::examineShadowState}} describing
the rationale.
> 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
