[
https://issues.apache.org/jira/browse/CASSANDRA-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-2584.
---------------------------------------
Resolution: Won't Fix
stopping / restarting the executor is a lot more work for the rest of the code
base (need to deal w/ rejected execution etc).
doesn't seem like a great place to spend complexity to me.
> When disabling or reducing compaction frequency, CopactionManager still shows
> frequent activity
> -----------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-2584
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2584
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Patricio Echague
> Priority: Trivial
>
> I was playing with different set of configurations to test performance. One
> of those was with compaction disabled.
> besides the fact that it is a bad practice to disable compaction, even when I
> did disable it, JConsole CompactionManager#completedTasks showed 30 tasks
> completed during the duration of my test.
> I think it would be good to stop the tasks from being executed. It looks like
> the executor is still executing the tasks with NO-OP.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
