cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-14802) calculatePendingRanges assigns more pending ranges than necessary
Date Wed, 06 Mar 2019 17:13:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-14802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16785881#comment-16785881
] 

Benedict commented on CASSANDRA-14802:
--------------------------------------

+1

bq. This isn't a new regression and getting it right (& validating it) is going to be
quite involved, so it feels a bit of a risk for the 4.0 timeframe.

FWIW, I will need to look at this class again soon because transient replication complicated
it, and it is known to not work with transient replication.  In the process, I may see how
challenging it would be to more comprehensively fix and test the class, as it is currently
very non-obvious to work with.  It might be possible to formulate it in a clearer manner,
but we'll see; obviously, not if it risk 4.0.

> 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
>            Priority: Major
>             Fix For: 4.x
>
>
> 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
(v7.6.3#76005)

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


Mime
View raw message