cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7402) Add metrics to track memory used by client requests
Date Tue, 07 Oct 2014 18:19:34 GMT

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

T Jake Luciani commented on CASSANDRA-7402:
-------------------------------------------

I will rename to atomSize().  I also want to run a benchmark to see what kind of impact this
has on perf

> 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
>              Labels: ops, performance, stability
>             Fix For: 2.1.1
>
>         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)

Mime
View raw message