[
https://issues.apache.org/jira/browse/CASSANDRA-19262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Petrov updated CASSANDRA-19262:
------------------------------------
Fix Version/s: 5.1
Since Version: 5.1
Source Control Link:
https://github.com/apache/cassandra/commit/1cb6d3568b0ab9c7ea5a90b56e680d5b79c1d216
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed to trunk with
[1cb6d3568b0ab9c7ea5a90b56e680d5b79c1d216|https://github.com/apache/cassandra/commit/1cb6d3568b0ab9c7ea5a90b56e680d5b79c1d216]
> 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
> Fix For: 5.1
>
> Attachments: ci_summary-1.html, result_details.tar.gz
>
>
> 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, there are
> two independent 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
