cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10866) Column Family should expose latency metrics for dropped mutations.
Date Wed, 16 Dec 2015 00:36:46 GMT

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

Paulo Motta commented on CASSANDRA-10866:
-----------------------------------------

I don't see much sense in exposing latency metrics for dropped mutations on a per-cf basis,
since this won't vary much on a per-cf basis, but rather on a per-node basis (also internal
vs cross node), so the global dropped mutation latency metric should suffice to tune node
timeouts accordingly. Keeping a count for dropped mutations per CF may make sense though,
as you may want to monitor the distribution of dropped mutations across different CFs.

> Column Family should expose latency metrics for dropped mutations.
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-10866
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10866
>             Project: Cassandra
>          Issue Type: Improvement
>         Environment: PROD
>            Reporter: Anubhav Kale
>            Priority: Minor
>
> Please take a look at the discussion in CASSANDRA-10580. This is opened so that the latency
on dropped mutations is exposed as a metric on column families.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message