cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-465) nodeprobe setcompactionthreshold <Max> does not allow zero
Date Thu, 08 Oct 2009 12:36:31 GMT

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

Hudson commented on CASSANDRA-465:
----------------------------------

Integrated in Cassandra #221 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/221/])
    Added the ability to set maxthreshold to zero in nodeprobe, and added a special case to
CF.doCompaction to not run compaction when its disabled. patch by goffinet; reviewed by jbellis
for 


> nodeprobe setcompactionthreshold <Max> does not allow zero
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-465
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-465
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.5
>            Reporter: Chris Goffinet
>            Assignee: Chris Goffinet
>            Priority: Minor
>             Fix For: 0.5
>
>         Attachments: 0001-Allow-maxthreshold-to-be-greater-than-zero-v2.patch, 0001-Allow-maxthreshold-to-be-greater-than-zero-v3.patch,
0001-Allow-maxthreshold-to-be-greater-than-zero-v4.patch, 0001-CASSANDRA-465.-Allow-maxthreshold-to-be-set-to-zero.patch
>
>
> We should allow setting maxthreshold to zero.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message