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

Patrick Bannister commented on CASSANDRA-13889:
-----------------------------------------------

This is coming along nicely. Please see the attached files 
sample_output_normal.txt, sample_output_sorted.txt, and 
sample_output_sorted_top3.txt for examples of output from the current 
implementation.

There's some further work needed to implement additional sorting keys and 
update documentation. Development has been test-first so far, so unit testing 
is mostly finished. I also anticipate some minor work to adapt to 
CASSANDRA-14340.

 

> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to