cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Gazzarini (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5074) Add an official way to disable compaction
Date Thu, 21 Feb 2013 12:10:13 GMT


Andrea Gazzarini commented on CASSANDRA-5074:

Probably that wasn't clear, but honestly I believe it's a problem of mine: I have just a little
bit of experience on Cassandra source code and its internal architecture. 

Ok, now I think I got the point about your idea, so I will continue investigating the code
in order to implement that. 

A question: in case the logic is moved on the CompactionMananger, what should be, from client
point of view, a nice and good way to indicate that the (background) compaction must be disabled?
I believe the command line of my previous post is no longer appropriate

> create column family XYZ with compaction_strategy=NoCompactionStrategy 

> Add an official way to disable compaction
> -----------------------------------------
>                 Key: CASSANDRA-5074
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Priority: Minor
>             Fix For: 1.2.2
> We've traditionally used "min or max compaction threshold = 0" to disable compaction,
but this isn't exactly intuitive and it's inconsistently implemented -- allowed from jmx,
not allowed from cli.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message