cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13645) Optimize the number of replicas required in Quorum read/write
Date Thu, 29 Jun 2017 00:21:00 GMT

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

Brandon Williams commented on CASSANDRA-13645:
----------------------------------------------

I think CL.TWO and CL.THREE cover your examples, however it may be time to think about CL.INTEGER
with a parameter, because obviously we don't want to keep enumerating there and times eventually
change.

> Optimize the number of replicas required in Quorum read/write
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-13645
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13645
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Coordination
>            Reporter: Dikang Gu
>            Assignee: Dikang Gu
>             Fix For: 4.x
>
>
> Currently, for C* read/write requests with quorum consistent level, number of replicas
required for quorum write is W=N/2+1, and number of replicas required for quorum read is R=N/2+1
as well. 
> It works fine in odd number of replicas case, which R + W = N + 1, but in even number
of replicas case, like RF=4, 6, 8, the R+W = N + 2, which means we are having two overlapping
nodes in read/write requests, which is not necessary. It can not provide strong consistency,
but will hurts P99 read latency a lot (2X in our production cluster).
> In a lot of other database, like Amazon Aurora, they use W = N/2 + 1 and R = N/2 for
quorum requests, which will provide enough strong consistency, but talk to one less replica
in read path. "We use a quorum model with 6 votes (V = 6), a write quorum of 4/6 (Vw = 4),
and a read quorum of 3/6 (Vr = 3)."
> I propose we do the same optimization, change read quorum to talk to N/2 replicas, which
should reduce the read latency for quorum read in general.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message