[
https://issues.apache.org/jira/browse/CASSANDRA-21142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18055130#comment-18055130
]
Sam Tunnicliffe commented on CASSANDRA-21142:
---------------------------------------------
Test failures seem to be largely previously-failing Accord tests or related to
CASSANDRA-20081 / CASSANDRA-21135. There is also an issue I'm working on with
python upgrade tests which do a concurrent bounce of the cluster, rather than a
rolling upgrade. I'll hopefully have a patch for that soon.
> 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: 5.x
>
> Attachments: ci_summary.html, result_details.tar.gz
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
