cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Bannister (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13889) cfstats should take sorting and limit parameters
Date Sun, 01 Apr 2018 01:51:00 GMT


Patrick Bannister commented on CASSANDRA-13889:

I'm thinking that command line usage should support sort keys corresponding to the keys used
in the TableStatsHolder convert2Map function. They're more verbose than I'd like, but I felt
that creating a whole new nomenclature was the worse choice.

However, I am supporting a few alternative short forms for keys I expect to get common use:
 * "read_latency" as a short form of "local_read_latency_ms"
 * "reads" as a short form of "local_read_count"
 * "write_latency" as a short form of "local_write_latency_ms"
 * "writes" as a short form of "local_write_count"

I cringe a bit at "average_live_cells_per_slice_last_five_minutes", but I also didn't want
to blow up the command line usage hint with alternate short forms of every key.

> cfstats should take sorting and limit parameters
> ------------------------------------------------
>                 Key: CASSANDRA-13889
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message