[
https://issues.apache.org/jira/browse/CASSANDRA-19671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885365#comment-17885365
]
Stefan Miklosovic commented on CASSANDRA-19671:
-----------------------------------------------
I think we should do it like this
https://github.com/apache/cassandra/pull/3582
keyspace metrics already contain total and live disk space used. We do not need
to sum it up from all column families. It is already there on keyspace level,
it does it automatically. The problem is that in keyspace metrics, that metric
is a gauge instead of a counter so when called from node probe it was failing,
I had to tweak it a little bit so when we ask for keyspace metric it will fetch
it for a gauge, not counter.
[~bschoeni] is this OK for your, would you test that? We can build afterwards.
> Nodetool tabestats: add keyspace space used and table r/w ratio
> ---------------------------------------------------------------
>
> Key: CASSANDRA-19671
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19671
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
> Reporter: Brad Schoening
> Assignee: Arun Ganesh
> Priority: Low
> Attachments: plaintext-humanreadable.txt, plaintext.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Nodetool tabestats reports the space used live and total per table, but not
> for the entire keyspace. This would be useful information.
> Also, in the table level stats, it would be useful to have the read/write
> ratio. This metric is important in choosing compaction strategies such as
> LCS.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
