You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org> on 2012/03/21 12:37:39 UTC
[jira] [Commented] (CASSANDRA-4070) CFS.setMaxCompactionThreshold
doesn't allow 0 unless min is also 0
[ https://issues.apache.org/jira/browse/CASSANDRA-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234286#comment-13234286 ]
Jonathan Ellis commented on CASSANDRA-4070:
-------------------------------------------
+1, but for the record using min/max as "disable compaction" signal is kind of broken.
> CFS.setMaxCompactionThreshold doesn't allow 0 unless min is also 0
> ------------------------------------------------------------------
>
> Key: CASSANDRA-4070
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4070
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Trivial
> Fix For: 1.0.9
>
> Attachments: 4070.patch
>
>
> Thrift allows to set the max compaction threshold to 0 to disable compaction. However, CFS.setMaxCompactionThreshold throws an exception min > max even if max is 0.
> Note that even if someone sets 0 for both the min and max thresholds, we'll can have a problem because SizeTieredCompaction calls CFS.setMaxCompactionThreshold before calling CFS.setMinCompactionThreshold and thus will trigger the RuntimeException when it shouldn't.
--
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