[
https://issues.apache.org/jira/browse/CASSANDRA-10805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184916#comment-15184916
]
Stefan Podkowinski commented on CASSANDRA-10805:
------------------------------------------------
This looks really promising. I've played around with the branch and did some
minor changes in a [PR|https://github.com/carlyeks/cassandra/pull/1/files].
However, I'm still not sure why you plan to implement your own file rolling
logic. Getting files rolled by logback and archive them manually afterwards
would work perfectly fine for me.
> 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.x
>
>
> 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)
