You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2016/06/03 15:14:59 UTC

[jira] [Updated] (CASSANDRA-11908) Track message sizes for dropped mutations

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

Aleksey Yeschenko updated CASSANDRA-11908:
------------------------------------------
    Component/s: Observability

> Track message sizes for dropped mutations
> -----------------------------------------
>
>                 Key: CASSANDRA-11908
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11908
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Observability
>            Reporter: Jeremiah Jordan
>
> CASSANDRA-10580 and a couple other recent tickets have added more stats for tracking dropped messages, it would be good to add the sizes of the messages being dropped to those stats.  One of the main things I have seen that can lead to stuff taking a long time is just things being too big, it would be nice to be able to tell if that was the problem from the dropped messages logs and JMX stats.



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