cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3666) Changing compaction strategy from Leveled to SizeTiered puts the node down
Date Fri, 23 Dec 2011 20:12:31 GMT

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

Jonathan Ellis commented on CASSANDRA-3666:
-------------------------------------------

Were there any error messages logged?
                
> Changing compaction strategy from Leveled to SizeTiered puts the node down
> --------------------------------------------------------------------------
>
>                 Key: CASSANDRA-3666
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3666
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.0.6
>         Environment: Windows Server 2008 R2 64bit
>            Reporter: Viktor Jevdokimov
>
> When column family compaction strategy is changed from Leveled to SizeTiered and there're
Leveled compaction tasks pending, Cassandra starting to flood in logs with thousands per sec
messages:
> Nothing to compact in ColumnFamily1.  Use forceUserDefinedCompaction if you wish to force
compaction of single sstables (e.g. for tombstone collection)
> As a result, log disk is full and system is down.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message