[jira] [Commented] (CASSANDRA-7402) Add metrics to track memory used by client requests

["Aleksey Yeschenko (JIRA)" <ji...@apache.org>]

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

Aleksey Yeschenko commented on CASSANDRA-7402:
----------------------------------------------

bq. Any update on this? Seems like a valuable addition to help identify problems.

It's blocked by lack of a performance impact benchmark.

> Add metrics to track memory used by client requests
> ---------------------------------------------------
>
>                 Key: CASSANDRA-7402
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7402
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: T Jake Luciani
>            Assignee: T Jake Luciani
>            Priority: Minor
>              Labels: ops, performance, stability
>             Fix For: 2.1.x
>
>         Attachments: 7402.txt
>
>
> When running a production cluster one common operational issue is quantifying GC pauses caused by ongoing requests.
> Since different queries return varying amount of data you can easily get your self into a situation where you Stop the world from a couple of bad actors in the system.  Or more likely the aggregate garbage generated on a single node across all in flight requests causes a GC.
> It would be very useful for operators to see how much garbage the system is using to handle in flight mutations and queries. 
> It would also be nice to have either a log of queries which generate the most garbage so operators can track this.  Also a histogram.



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