[jira] [Resolved] (CASSANDRA-8195) Tools for discovering problem/largest partitions

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

     [ https://issues.apache.org/jira/browse/CASSANDRA-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko resolved CASSANDRA-8195.
------------------------------------------
    Resolution: Duplicate

> Tools for discovering problem/largest partitions
> ------------------------------------------------
>
>                 Key: CASSANDRA-8195
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8195
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Matt Stump
>
> A very common problem is that a customer will have one or two very hot partitions. This could be a result of an unforeseen usage pattern or a problem user. Tracking down the offending parition/row currently involves a linear scan of the data. 
> We should keep stats on the largest N partitions encountered and make those visible via nodetool as we do with cfhistograms. A reasonable suggestion for N is 10, meaning the top 10 partition keys and their size would be visible. We should also probably keep this info as part of the sstable metadata.



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