cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sarath P S (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-13771) Emit metrics whenever we hit tombstone failures and warn thresholds
Date Wed, 06 Sep 2017 11:36:00 GMT

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

Sarath P S edited comment on CASSANDRA-13771 at 9/6/17 11:35 AM:
-----------------------------------------------------------------

Moved tombstone WARN and FAILURE metrics to TableMetrics, Attaching 0001-Emit-metrics-whenever-we-hit-tombstone-failures-and-.patch


was (Author: sarath.ps):
Moved tombstone WARN and FAILURE metrics to TableMetrics

> Emit metrics whenever we hit tombstone failures and warn thresholds
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-13771
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13771
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: TIRU ADDANKI
>            Assignee: Sarath P S
>            Priority: Minor
>             Fix For: 4.x
>
>         Attachments: 0001-Emit-metrics-whenever-we-hit-tombstone-failures-and-.patch,
13771.patch
>
>
> Many a times we see cassandra timeouts, but unless we check the logs we won’t be able
to tell if the time outs are result of too many tombstones or some other issue. It would be
easier if we have metrics published whenever we hit tombstone failure/warning thresholds.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message