You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Minal Kyada (Jira)" <ji...@apache.org> on 2026/07/10 21:11:00 UTC

[jira] [Updated] (CASSANDRA-21503) System peers tables may be incorrectly repaired during a rolling upgrade.

     [ https://issues.apache.org/jira/browse/CASSANDRA-21503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Minal Kyada updated CASSANDRA-21503:
------------------------------------
    Fix Version/s: 6.x
                   7.x

> System peers tables may be incorrectly repaired during a rolling upgrade.
> -------------------------------------------------------------------------
>
>                 Key: CASSANDRA-21503
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21503
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Transactional Cluster Metadata
>            Reporter: Minal Kyada
>            Assignee: Minal Kyada
>            Priority: Normal
>             Fix For: 6.x, 7.x
>
>
> During a rolling upgrade from 4.0.4 to 4.0.5, the system peers tables are expected to be temporarily divergent from ClusterMetadata. Nodes still on 4.0.4 have not yet registered with TCM, so their peer table entries are not fully reflected in ClusterMetadata.directory.
> SystemPeersValidator.validateAndRepair() does not account for this window, making it possible for the peers tables to end up in an incorrect state where valid peer entries have been removed or overwritten.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org