You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (Jira)" <ji...@apache.org> on 2024/06/17 15:11:00 UTC

[jira] [Updated] (CASSANDRA-19709) Always repair the full range when repairing system_cluster_metadata

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

Marcus Eriksson updated CASSANDRA-19709:
----------------------------------------
    Change Category: Operability
         Complexity: Low Hanging Fruit
      Fix Version/s: 5.1-alpha1
          Reviewers: Marcus Eriksson
             Status: Open  (was: Triage Needed)

CI results in CASSANDRA-19713

> Always repair the full range when repairing system_cluster_metadata
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-19709
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19709
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Transactional Cluster Metadata
>            Reporter: Marcus Eriksson
>            Assignee: Sam Tunnicliffe
>            Priority: Normal
>             Fix For: 5.1-alpha1
>
>
> Since system_cluster_metadata uses a custom partitioner we need to repair the full range whenever an operator uses -st and -et tokens to avoid breaking existing repair automations. This is fine since the amount of data in this keyspace should be small.
> https://github.com/krummas/cassandra/commit/6ab8fcd1126f67b0117e1ee3c1fd1d4b40ac2362



--
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