You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Carl Yeksigian (JIRA)" <ji...@apache.org> on 2016/01/04 21:39:39 UTC
[jira] [Commented] (CASSANDRA-10805) Additional Compaction Logging
[ https://issues.apache.org/jira/browse/CASSANDRA-10805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081762#comment-15081762 ]
Carl Yeksigian commented on CASSANDRA-10805:
--------------------------------------------
* I was initially using logback, but changed because I was getting incomplete files (since I didn't know when a new file was created). Looking at the [logback docs|http://logback.qos.ch/manual/appenders.html#RollingFileAppender] it seems like I probably just need to implement these two classes to make sure the logs are complete
* That will work well; I'll make sure the logger has the name of the table it is assigned to in order to capture just the output from one table
* Good point; this could also simplify some of the multiple-line events
> 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
>
> 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)