[
https://issues.apache.org/jira/browse/CASSANDRA-13889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16459378#comment-16459378
]
Patrick Bannister commented on CASSANDRA-13889:
-----------------------------------------------
[~krummas], it looks like the failure is caused by the stat "Old SSTable
count," which doesn't appear in the test's expected output for tablestats. I
don't recognize that stat - are you testing changes that include modifications
to TableStatsPrinter?
For what it's worth, I synced my fork with the trunk branch on the
apache/cassandra repo and reran these tests, and they still pass in trunk on my
environment (Ubuntu 16.04 LTS on a 64-bit architecture).
> 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: 13889-trunk.txt, 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
