[
https://issues.apache.org/jira/browse/CASSANDRA-21187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18065319#comment-18065319
]
Sam Tunnicliffe edited comment on CASSANDRA-21187 at 3/12/26 10:02 AM:
-----------------------------------------------------------------------
That CI run looks like it's for a different branch - the ci_summary.html
suggests it was run against -the current HEAD of trunk- an older commit on
trunk. Did you attach the wrong files by mistake?
was (Author: beobal):
That CI run looks like it's for a different branch - the ci_summary.html
suggests it was run against the current HEAD of trunk. Did you attach the wrong
files by mistake?
> Make sure system.peers and peers_v2 match cluster metadata
> ----------------------------------------------------------
>
> Key: CASSANDRA-21187
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21187
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Cluster/Membership
> Reporter: Minal Kyada
> Assignee: Minal Kyada
> Priority: Normal
> Fix For: 6.x
>
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> We should check that peers and peers_v2 match cluster metadata, either on
> startup or potentially every time we update those tables
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]