Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 28 Oct 2016 08:34:58 +0000 (UTC)
From: "Romain Hardouin (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13005330.1473994161000.115479.1477643698534@Atlassian.JIRA>
In-Reply-To: <JIRA.13005330.1473994161000@Atlassian.JIRA>
References: <JIRA.13005330.1473994161000@Atlassian.JIRA> <JIRA.13005330.1473994161684@arcas>
Subject: [jira] [Commented] (CASSANDRA-12649) Add BATCH metrics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 28 Oct 2016 08:35:00 -0000


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

Romain Hardouin commented on CASSANDRA-12649:
---------------------------------------------

Yes, these metrics are useful.
Unfortunately the patch doesn't merge anymore neither to cassandra-3.X branch nor to the trunk.

> Add BATCH metrics
> -----------------
>
>                 Key: CASSANDRA-12649
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12649
>             Project: Cassandra
>          Issue Type: Wish
>            Reporter: Alwyn Davis
>            Priority: Minor
>             Fix For: 3.x
>
>         Attachments: trunk-12649.txt
>
>
> To identify causes of load on a cluster, it would be useful to have some additional metrics:
> * *Mutation size distribution:* I believe this would be relevant when tracking the performance of unlogged batches.
> * *Logged / Unlogged Partitions per batch distribution:* This would also give a count of batch types processed. Multiple distinct tables in batch would just be considered as separate partitions.


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