[jira] [Updated] (CASSANDRA-21142) Consensus groups for range movements can omit future owners of merging ranges

["Sam Tunnicliffe (Jira)" <ji...@apache.org>]

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

Sam Tunnicliffe updated CASSANDRA-21142:
----------------------------------------
     Bug Category: Parent values: Correctness(12982)Level 1 values: Consistency(12989)
       Complexity: Low Hanging Fruit
    Discovered By: Code Inspection
    Fix Version/s: 6.x
         Severity: Normal
           Status: Open  (was: Triage Needed)

> Consensus groups for range movements can omit future owners of merging ranges
> -----------------------------------------------------------------------------
>
>                 Key: CASSANDRA-21142
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21142
>             Project: Apache Cassandra
>          Issue Type: Bug
>          Components: Transactional Cluster Metadata
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Normal
>             Fix For: 6.x
>
>
> The consensus group for a range movement operation is union of current and future replicas for all affected ranges. However, when the movement includes a merge of existing ranges (i.e. a node leaving or moving) the future replicas are incorrectly calculated. If a node's only involvement in the operation is to acquire the new merged range, it isn't included in the consensus group.



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