[
https://issues.apache.org/jira/browse/CASSANDRA-16844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551234#comment-17551234
]
David Capwell edited comment on CASSANDRA-16844 at 6/7/22 7:02 PM:
-------------------------------------------------------------------
So how do people feel about moving forward? I see the following options
1) revert
2) add behind a feature flag (something like nodetool compactionstats
--show-sstables)
3) move to the end and hope for the best
thoughts?
was (Author: dcapwell):
So how do people feel about moving forward? I see the following options
1) revert
2) add behind a feature flag (something like nodetool compactionstats
--show-sstables)
thoughts?
> Add number of sstables in a compaction to compactionstats output
> ----------------------------------------------------------------
>
> Key: CASSANDRA-16844
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16844
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
> Reporter: Brendan Cicchi
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 4.1, 4.1-alpha1
>
>
> It would be helpful to know at a glance how many sstables are involved in any
> running compactions. While this information can certainly be collected now, a
> user has to grab it from the debug logs. I think it would be helpful for some
> use cases to have this information straight from {{nodetool compactionstats}}
> and then if the actual sstables involved in the compactions are desired, dive
> into the debug.log for that. I think it would also be good to have this
> information in the output of {{nodetool compactionhistory}}.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
