[
https://issues.apache.org/jira/browse/CASSANDRA-19262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-19262:
------------------------------------
Test and Documentation Plan: Includes new MIN_TOKEN stress test
Status: Patch Available (was: Open)
> Handle MIN_TOKEN placement correctly
> ------------------------------------
>
> Key: CASSANDRA-19262
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19262
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Bootstrap and Decommission
> Reporter: Alex Petrov
> Assignee: Alex Petrov
> Priority: Normal
> Attachments: ci_summary.html, ci_summary.json
>
>
> During concurrent range movements, it is possible to end up in a situation
> when from the perspective of the node that owns the {{MIN}} token, the there
> are to ranges {{(MIN, A]}} and {{(Z, MIN]}}. And from the perspective of the
> joining node, it does not know that these are two _separate_ ranges, and
> thinks they are just one wraparound range, so it tries to just add some
> placements there.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
