cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3342) cassandra-cli allows setting min_compaction_threshold to 1
Date Tue, 11 Oct 2011 01:06:29 GMT

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

Brandon Williams commented on CASSANDRA-3342:
---------------------------------------------

ISTM the easiest thing to do here is actually use 2 when a user specifies 1.
                
> cassandra-cli allows setting min_compaction_threshold to 1
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-3342
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3342
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 0.8.6
>         Environment: Linux 2.6.32-131.6.1.el6.x86_64 #1 SMP Mon Jun 20 14:15:38 EDT 2011
x86_64 x86_64 x86_64 GNU/Linux (RHEL 6)
>            Reporter: Jason Baker
>
> {{
> [root@Apture] update column family MagicLinks with min_compaction_threshold=1 and max_compaction_threshold=20;
> b98e3b80-f3a3-11e0-0000-76abb4a6dbbf
> Waiting for schema agreement...
> ... schemas agree across the cluster
> }}
> I'm told that a min_compaction_threshold of 1 is nonsensical.  I had a spell where my
servers stopped doing compactions.  Once I upped the min_compaction_threshold, they started
compacting again.  I'm unable to confirm for sure that this was the case.

--
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