[
https://issues.apache.org/jira/browse/CASSANDRA-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178755#comment-13178755
]
Sylvain Lebresne commented on CASSANDRA-3666:
---------------------------------------------
+1 on the patch (but we can wait on Viktor to confirm it does fix it for him).
(I actually think that it's the settings of the threshold in LCS that is the
ugly part, but let's not bother with that)
> Changing compaction strategy from Leveled to SizeTiered logs millions of
> messages about nothing to compact
> ----------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-3666
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3666
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.0.0
> Environment: Windows Server 2008 R2 64bit
> Reporter: Viktor Jevdokimov
> Assignee: Jonathan Ellis
> Labels: compaction
> Fix For: 1.0.7
>
> Attachments: 3666.txt
>
>
> 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
