You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2018/10/03 11:22:00 UTC
[jira] [Created] (CASSANDRA-14801) calculatePendingRanges no longer
safe for multiple adjacent range movements
Benedict created CASSANDRA-14801:
------------------------------------
Summary: calculatePendingRanges no longer safe for multiple adjacent range movements
Key: CASSANDRA-14801
URL: https://issues.apache.org/jira/browse/CASSANDRA-14801
Project: Cassandra
Issue Type: Bug
Components: Coordination, Distributed Metadata
Reporter: Benedict
Fix For: 4.0
Correctness depended upon the narrowing to a {{Set<InetAddressAndport>}}, which we no longer do - we maintain a collection of all {{Replica}}. Our {{RangesAtEndpoint}} collection built by {{getPendingRanges}} can as a result contain the same endpoint multiple times; and our {{EndpointsForToken}} obtained by {{TokenMetadata.pendingEndpointsFor}} may fail to be constructed, resulting in cluster-wide failures for writes to the affected token ranges for the duration of the range movement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org