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 2010/06/23 18:28:51 UTC

[jira] Commented: (CASSANDRA-1181) kinder gentler compaction

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

Jonathan Ellis commented on CASSANDRA-1181:
-------------------------------------------

using thread priority makes that unnecessary.  that is why it's a better solution.

> kinder gentler compaction
> -------------------------
>
>                 Key: CASSANDRA-1181
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1181
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Jonathan Ellis
>            Assignee: Brandon Williams
>             Fix For: 0.7
>
>         Attachments: CompactionManager.java
>
>
> I suggested this in a ML thread but it seems that nobody actually tried it.  I think it's worth following up on:
> You could try setting the compaction thread to a lower priority.  You could add a thread priority to NamedThreadPool, and pass that up from CompactionExecutor constructor.  According to http://www.javamex.com/tutorials/threads/priority_what.shtml you have to run as root and add a JVM option to get this to work.
> In particular, Brandon saw stress.py read latencies spike to 100ms during [anti]compaction on a 2 core machine.  I'd like to see if this can mitigate that.

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