You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2022/05/31 23:26:00 UTC
[jira] [Updated] (CASSANDRA-17676) When a node is bootstrapping it gets the whole gossip state but applies in random order causing some cases where StorageService will fail causing an instance to not show up in TokenMetadata
[ https://issues.apache.org/jira/browse/CASSANDRA-17676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Capwell updated CASSANDRA-17676:
--------------------------------------
Bug Category: Parent values: Correctness(12982)Level 1 values: Recoverable Corruption / Loss(12986)
Complexity: Normal
Discovered By: Adhoc Test
Fix Version/s: 4.x
Severity: Normal
Status: Open (was: Triage Needed)
> When a node is bootstrapping it gets the whole gossip state but applies in random order causing some cases where StorageService will fail causing an instance to not show up in TokenMetadata
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17676
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17676
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Gossip
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.x
>
>
> When gossip state has a causal relationship, the order the state gets applied needs to match this relationship, and when it doesn’t it can cause bootstrap (which apply the whole state in an empty state) to see missing data or instances
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org