You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Lohfink (JIRA)" <ji...@apache.org> on 2018/09/11 20:53:00 UTC
[jira] [Comment Edited] (CASSANDRA-14694) add latency sample for
speculative read repair writes
[ https://issues.apache.org/jira/browse/CASSANDRA-14694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16611233#comment-16611233 ]
Chris Lohfink edited comment on CASSANDRA-14694 at 9/11/18 8:52 PM:
--------------------------------------------------------------------
there is a coordinator write latency per table, can it just use that instead of introducing new metric?
was (Author: cnlwsu):
there is a coordinator write latency per table, can it just use that instead?
> add latency sample for speculative read repair writes
> -----------------------------------------------------
>
> Key: CASSANDRA-14694
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14694
> Project: Cassandra
> Issue Type: Bug
> Reporter: Blake Eggleston
> Assignee: Blake Eggleston
> Priority: Major
> Fix For: 4.0
>
>
> Speculative read repair mutations shouldn't use read latencies to determine when to send a speculative mutation. It should have it's own value based on mutation latencies.
--
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