Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 7 Oct 2014 18:19:34 +0000 (UTC)
From: "T Jake Luciani (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12721421.1402927241000.210214.1412705974431@Atlassian.JIRA>
In-Reply-To: <JIRA.12721421.1402927241000@Atlassian.JIRA>
References: <JIRA.12721421.1402927241000@Atlassian.JIRA>
 <JIRA.12721421.1402927241886@arcas>
Subject: [jira] [Commented] (CASSANDRA-7402) Add metrics to track memory
 used by client requests
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ 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)