cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8094) Heavy writes in RangeSlice read requests
Date Tue, 03 May 2016 16:39:13 GMT

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

Sam Tunnicliffe commented on CASSANDRA-8094:
--------------------------------------------

Coming back to look at this now, I think that using {{extensions}} to persist the param is
just too hacky to be considered a reasonable approach. Given that, we should either defer
this ticket until 4.0 or prioritize CASSANDRA-11382, using this as a driver towards an implementation.


> Heavy writes in RangeSlice read  requests 
> ------------------------------------------
>
>                 Key: CASSANDRA-8094
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8094
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Minh Do
>            Assignee: Sam Tunnicliffe
>              Labels: lhf
>             Fix For: 3.x
>
>
> RangeSlice requests always do a scheduled read repair when coordinators try to resolve
replicas' responses no matter read_repair_chance is set or not.
> Because of this, in low writes and high reads clusters, there are very high write requests
going on between nodes.  
> We should have an option to turn this off and this can be different than the read_repair_chance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message