You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/12/11 19:41:21 UTC
[jira] [Resolved] (CASSANDRA-4997) Remove multithreaded_compaction
from cassandra.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-4997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-4997.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0 rc1
1.1.8
Assignee: Jonathan Ellis
added a warning referencing CASSANDRA-4492 instead of removing it entirely.
> Remove multithreaded_compaction from cassandra.yaml
> ---------------------------------------------------
>
> Key: CASSANDRA-4997
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4997
> Project: Cassandra
> Issue Type: Task
> Components: Core
> Affects Versions: 1.0.12, 1.1.6
> Reporter: Jeremy Hanna
> Assignee: Jonathan Ellis
> Priority: Trivial
> Fix For: 1.1.8, 1.2.0 rc1
>
>
> There have been several issues with multithreaded_compaction and it's generally discouraged for use, even on SSD based systems. It seems like it would be a good idea to remove it completely from the cassandra.yaml but leave it as a setting for now. That way people can manually add it, but unsuspecting people who don't know about the sharp edges won't enable it on their SSD based systems.
> An alternative to removing it from the cassandra.yaml is to add more warnings to the description.
--
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: http://www.atlassian.com/software/jira