Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Wed, 18 Jun 2014 18:38:25 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12714704.1400219215832.1734.1403116705190@arcas>
In-Reply-To: <JIRA.12714704.1400219215832@arcas>
References: <JIRA.12714704.1400219215832@arcas>
Subject: [jira] [Commented] (CASSANDRA-7247) Provide top ten most frequent
 keys per column family
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-7247:
-------------------------------------------

Using tracingProbability as a coarse on/off feels wrong to me.  I'd prefer one of these options:

# If it's cheap, just do it always
# If it makes sense to do it along with other tracing ops, trace if we've enabled a trace state already
# Otherwise, introduce a new per-table setting

> Provide top ten most frequent keys per column family
> ----------------------------------------------------
>
>                 Key: CASSANDRA-7247
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7247
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Chris Lohfink
>            Assignee: Chris Lohfink
>            Priority: Minor
>         Attachments: jconsole.png, patch.txt
>
>
> Since already have the nice addthis stream library, can use it to keep track of most frequent DecoratedKeys that come through the system using StreamSummaries ([nice explaination|http://boundary.com/blog/2013/05/14/approximate-heavy-hitters-the-spacesaving-algorithm/]).  Then provide a new metric to access them via JMX.  


--
This message was sent by Atlassian JIRA
(v6.2#6252)