cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh McKenzie (Jira)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-16880) Catch read repair timeouts and add metrics to indicate they occurred
Date Wed, 01 Sep 2021 15:49:00 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-16880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh McKenzie updated CASSANDRA-16880:
--------------------------------------
    Source Control Link: https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=7d59da4ab3e446606f0fe0cc73554ad12f674cd5
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

> 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
>            Priority: Normal
>             Fix For: 4.1
>
>
> 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


Mime
View raw message