[
https://issues.apache.org/jira/browse/CASSANDRA-13771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155233#comment-16155233
]
Marcus Eriksson commented on CASSANDRA-13771:
---------------------------------------------
Running unit tests here: https://circleci.com/gh/krummas/cassandra/104
and dtests here:
https://builds.apache.org/view/A-D/view/Cassandra/job/Cassandra-devbranch-dtest/284/
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
