[
https://issues.apache.org/jira/browse/CASSANDRA-20081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898537#comment-17898537
]
Maxwell Guo commented on CASSANDRA-20081:
-----------------------------------------
for compactionhistory：
a) is supported;
b) +1 with minor compaction type, besides, Why do we need to have these
information output requirements for level alone? What about STCS, TWCS， UCS? I
think we need to consider this in a unified way, list different strategies
their information is output.
c) +1
> Enhance nodetool compactionhistory to report compaction type and strategy
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-20081
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20081
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Brad Schoening
> Priority: Normal
>
> It would be useful for compactionhistory to report:
> a) the type of compaction, normal background compaction, garbagecollect by
> nodetool, or tombstone compaction (tombstone_threshold).
> b) the compaction strategy, STCS, LCS, or TWCS. For level, the from-level and
> to-level should be reported.
> c) also useful would be to make the bytes in and out human readable and add a
> -j option for machine readable json output.
>
> Finally, the meaning of rows_merged should be documented in
> [compactionhistory|[https://cassandra.apache.org/doc/stable/cassandra/tools/nodetool/compactionhistory.html].]
> A StackOverflow article provides one of the few descriptions [What does
> rows_merged mean in
> compactionhistory|https://stackoverflow.com/questions/27566558/what-does-rows-merged-mean-in-compactionhistory]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
