[jira] [Updated] (CASSANDRA-14802) calculatePendingRanges assigns more pending ranges than necessary

["Josh McKenzie (Jira)" <ji...@apache.org>]

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

Josh McKenzie updated CASSANDRA-14802:
--------------------------------------
    Status: Open  (was: Resolved)

Some how status: resolved w/Resolution: Unresolved. Re-opening to fix.

> calculatePendingRanges assigns more pending ranges than necessary 
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-14802
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14802
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Legacy/Coordination, Legacy/Distributed Metadata
>            Reporter: Benedict Elliott Smith
>            Assignee: Sam Tunnicliffe
>            Priority: Normal
>             Fix For: 4.0, 4.0-alpha1
>
>
> This might be a good thing, but should probably be configurable, and made consistent.  Presently, in a number of circumstances where there are multiple range movements, {{calculatePendingRanges}} will assign a pending range to a node that will not ultimately own it.  If done consistently, this might make range movements resilient to node failures / aborted range movements, since all nodes will be receiving all ranges they might own under any incomplete range ownership movements.  But done inconsistently it seems only to reduce availability in the cluster, by potentially increasing the number of pending nodes unnecessarily.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org