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 Elliott Smith (Jira)" <ji...@apache.org> on 2019/10/31 17:21:00 UTC
[jira] [Comment Edited] (CASSANDRA-14723) Increase write
availability during range movements
[ https://issues.apache.org/jira/browse/CASSANDRA-14723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964222#comment-16964222 ]
Benedict Elliott Smith edited comment on CASSANDRA-14723 at 10/31/19 5:20 PM:
------------------------------------------------------------------------------
I think this would also more robustly fix CASSANDRA-8346
was (Author: benedict):
I think this would also more robustly fix: 77df5578a0c80f9e8b5de914fa75d1bda023a4f5
> Increase write availability during range movements
> --------------------------------------------------
>
> Key: CASSANDRA-14723
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14723
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Coordination
> Reporter: Benedict Elliott Smith
> Priority: Normal
> Fix For: 4.x
>
>
> If pending ranges were to be paired with their ‘natural’ replicas, instead of requiring QUORUM+#pending, we could instead require QUORUM, but count both owners of the pending range as a combined 1 - where they are only counted if both return success.
> As an example, in a cluster with RF=3, a pending range movement would currently require 3 nodes to respond, so must include at least one of the pending nodes. Under the proposed scheme, the 2 non-participating nodes could respond as normal to reach a QUORUM, not requiring either of the pending nodes to respond.
--
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