[
https://issues.apache.org/jira/browse/CASSANDRA-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028386#comment-13028386
]
Jonathan Ellis commented on CASSANDRA-2558:
-------------------------------------------
bq. 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?
My rule of thumb is, re-open if the original fix is not yet released, otherwise
make a new ticket so it's clear that the original fix is in beta2 but the
follow-on is in rc1.
> 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
