[
https://issues.apache.org/jira/browse/CASSANDRA-14668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598791#comment-16598791
]
mck commented on CASSANDRA-14668:
---------------------------------
latest…
|| branch || testall || dtest ||
|
[CASSANDRA-14668|https://github.com/spodkowinski/cassandra/tree/CASSANDRA-14668]
|
[!https://circleci.com/gh/spodkowinski/cassandra/tree/CASSANDRA-14668.svg?style=svg!|https://circleci.com/gh/spodkowinski/cassandra/tree/CASSANDRA-14668]
|
[!https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/624/badge/icon!|https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/624/]
|
I'm +1 on the code.
In a system that has a badly stale node (causing many/most reads to RR) this
will create a lot of diagnostics events (when enabled), but that's the whole
point of being able to enable just specific diagnostic events.
> Diag events for read repairs
> ----------------------------
>
> Key: CASSANDRA-14668
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14668
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability
> Reporter: Stefan Podkowinski
> Assignee: Stefan Podkowinski
> Priority: Major
> Fix For: 4.x
>
>
> Read repairs have been a highly discussed topic during the last months and
> also saw some significant code changes. I'd like to be better prepared in
> case we need to investigate any further RR issues in the future, by adding
> diagnostic events that can be enabled for exposing informations such as:
> * contacted endpoints
> * digest responses by endpoint
> * affected partition keys
> * speculated reads / writes
> Â
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
