You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2014/08/23 03:21:11 UTC

[jira] [Comment Edited] (CASSANDRA-7818) Improve compaction logging

    [ https://issues.apache.org/jira/browse/CASSANDRA-7818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107744#comment-14107744 ] 

Benedict edited comment on CASSANDRA-7818 at 8/23/14 1:20 AM:
--------------------------------------------------------------

* It would be nice to give a user friendly id, like date + int (reset to zero each day), although perhaps not worth introducing new state over
* I'd like to cut out the full paths from files we print so we can more easily deal with larger compactions, and possibly print extra info like overlapping tables, without spamming the log too hard. File id + descriptor type should be enough


was (Author: benedict):
it would be nice to give a user friendly id, like date + int (reset to zero each day)
I'd like to cut out the full paths from files we print so we can more easily deal with larger compactions, and possibly print extra info like overlapping tables, without spamming the log too hard. File id + descriptor type should be enough

> Improve compaction logging
> --------------------------
>
>                 Key: CASSANDRA-7818
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7818
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Marcus Eriksson
>            Priority: Minor
>              Labels: compaction, lhf
>             Fix For: 2.1.1
>
>
> We should log more information about compactions to be able to debug issues more efficiently
> * give each CompactionTask an id that we log (so that you can relate the start-compaction-messages to the finished-compaction ones)
> * log what level the sstables are taken from



--
This message was sent by Atlassian JIRA
(v6.2#6252)