[
https://issues.apache.org/jira/browse/CASSANDRA-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901628#action_12901628
]
Jonathan Ellis commented on CASSANDRA-1181:
-------------------------------------------
let's make priority=1 the default, and add the jvm options to cassandra-env.sh
should we reject setting compaction to higher priority than NORMAL? no idea
what will happen if you do higher-than-normal on a JVM as non-root, since we've
explicitly defeated its protection against doing that :)
> kinder gentler compaction
> -------------------------
>
> Key: CASSANDRA-1181
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1181
> Project: Cassandra
> Issue Type: Task
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Brandon Williams
> Fix For: 0.6.3
>
> Attachments: 1181-trunk.txt, 1181.txt, CompactionManager.java,
> stats.txt
>
>
> 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.
