You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2022/04/07 20:49:00 UTC

[jira] [Commented] (CASSANDRA-17471) Provide JMX endpoint for transient full logging of blocking read repairs

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

David Capwell commented on CASSANDRA-17471:
-------------------------------------------

sorry I missed this for so long, sent feedback in the form of a commit; switched to nanos from currentTimeMillis to better handle funky clocks

> Provide JMX endpoint for transient full logging of blocking read repairs
> ------------------------------------------------------------------------
>
>                 Key: CASSANDRA-17471
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17471
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Observability/Logging
>            Reporter: Josh McKenzie
>            Assignee: Josh McKenzie
>            Priority: Normal
>
> While working with live clusters that have elevated blocking read repairs (a not uncommon scenario), it'd be helpful to have the ability to enable full logging of blocking read repairs for a finite amount of time to get insight into what's going on without having to heavily disrupt a cluster with a bounce or config change.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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