[ https://issues.apache.org/jira/browse/CASSANDRA-10805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Yeksigian resolved CASSANDRA-10805. ---------------------------------------- Resolution: Fixed Fix Version/s: (was: 3.x) 3.6 Thanks, [~krummas]. Commited as [e16d8a7|https://git-wip-us.apache.org/repos/asf/cassandra/?p=cassandra.git;a=commit;h=e16d8a7a667d50271a183a95be894126cb2a5414]. > Additional Compaction Logging > ----------------------------- > > Key: CASSANDRA-10805 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10805 > Project: Cassandra > Issue Type: New Feature > Components: Compaction, Observability > Reporter: Carl Yeksigian > Assignee: Carl Yeksigian > Priority: Minor > Fix For: 3.6 > > > Currently, viewing the results of past compactions requires parsing the log > and looking at the compaction history system table, which doesn't have > information about, for example, flushed sstables not previously compacted. > This is a proposal to extend the information captured for compaction. > Initially, this would be done through a JMX call, but if it proves to be > useful and not much overhead, it might be a feature that could be enabled for > the compaction strategy all the time. > Initial log information would include: > - The compaction strategy type controlling each column family > - The set of sstables included in each compaction strategy > - Information about flushes and compactions, including times and all involved > sstables > - Information about sstables, including generation, size, and tokens > - Any additional metadata the strategy wishes to add to a compaction or an > sstable, like the level of an sstable or the type of compaction being > performed -- This message was sent by Atlassian JIRA (v6.3.4#6332)