Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 3 May 2011 19:41:03 +0000 (UTC)
From: "Terje Marthinussen (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <301497919.19557.1304451663361.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1161959529.1741.1303803363304.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-2558) Add "concurrent_compactions"
 configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Terje Marthinussen commented on CASSANDRA-2558:
-----------------------------------------------

Sorry, did not watch this the last few days, but yes, it was a special case that triggered this, however, the fact that I managed to trigger it, means that I would like to be protected against it.

Just started a system with beta2 code, and so far, it seems like it works.

There are however a couple of tiny issues:
You still have a "compacters" in the sample config file.
#concurrent_compacters: 1

I also see that when I set compactors to 6, I get 7 tmp files. 
I would guess that is not intentional but a small offset problem?

I was looking for some sort of FAQ or something on this, so just a small side question.
Should issues with a patch be reported in the same jira once set to resolved or should I really make a new one in this case?


> Add "concurrent_compactions" configuration
> ------------------------------------------
>
>                 Key: CASSANDRA-2558
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2558
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.8 beta 1
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Trivial
>             Fix For: 0.8.0 beta 2
>
>         Attachments: 0001-Make-compaction-thread-number-configurable-v2.patch, 0001-Make-compaction-thread-number-configurable.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> We should expose a way to configure the max number of thread to use when multi_threaded compaction is turned on. So far, it uses nb_of_processors thread, which if you have many cores may be unreasonably high (as far as random IO is concerned and thus independently of compaction throttling)... at least unless you have SSD.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira