[ https://issues.apache.org/jira/browse/CASSANDRA-17471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17510736#comment-17510736 ]
Josh McKenzie commented on CASSANDRA-17471: ------------------------------------------- [PR|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/185/workflows/f185d636-4af8-40d8-8f87-fbeba0c84cd6] [JDK8 CI|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/185/workflows/ea3548a5-3903-47be-a50a-83a39bffd4b6] [JDK11 CI|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/185/workflows/f185d636-4af8-40d8-8f87-fbeba0c84cd6] > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org