You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Patrick Bannister (JIRA)" <ji...@apache.org> on 2018/03/29 02:35:00 UTC

[jira] [Updated] (CASSANDRA-13889) cfstats should take sorting and limit parameters

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

Patrick Bannister updated CASSANDRA-13889:
------------------------------------------
    Attachment: sample_output_sorted_top3.txt
                sample_output_sorted.txt
                sample_output_normal.txt

> cfstats should take sorting and limit parameters
> ------------------------------------------------
>
>                 Key: CASSANDRA-13889
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13889
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Jon Haddad
>            Assignee: Patrick Bannister
>            Priority: Major
>             Fix For: 4.0
>
>         Attachments: sample_output_normal.txt, sample_output_sorted.txt, sample_output_sorted_top3.txt
>
>
> When looking at a problematic node I'm not familiar with, one of the first things I do is check cfstats to identify the tables with the most reads, writes, and data.  This is fine as long as there aren't a lot of tables but once it goes above a dozen it's quite difficult.  cfstats should allow me to sort the results and limit to top K tables.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org