You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Josh McKenzie (Jira)" <ji...@apache.org> on 2021/08/24 16:05:00 UTC
[jira] [Created] (CASSANDRA-16880) Catch read repair timeouts and
add metrics to indicate they occurred
Josh McKenzie created CASSANDRA-16880:
-----------------------------------------
Summary: Catch read repair timeouts and add metrics to indicate they occurred
Key: CASSANDRA-16880
URL: https://issues.apache.org/jira/browse/CASSANDRA-16880
Project: Cassandra
Issue Type: Improvement
Components: Observability/Metrics
Reporter: Josh McKenzie
Assignee: Josh McKenzie
When we fire off async read repairs onto their own executor they may time out and in doing so, we don't have anything that stops them from propagating that timeout exception the way up to CassandraDaemon's uncaught exception handler. When this happens we logs at ERROR.
Obviously a timeout isn't great, but it's not an ERROR, so we should trap them instead and add some metrics around this occurrance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org