[
https://issues.apache.org/jira/browse/CASSANDRA-11894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuki Morishita resolved CASSANDRA-11894.
----------------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 3.0.x)
(was: 3.x)
Since 2.1 we moved to shared executor model (CASSANDRA-4718). So these JMX
operations are not supported in 2.1 anymore.
For 2.2+, those are not changeable.
What we could do is to add message to {{UnsupportedOperationException}} telling
the change is not supported, but at this stage of 2.1, I think the change is
not critical enough to be fixed.
> Changing MaximumThreads for ReadStage and MutationStage using JConsole
> returns 'java.lang.UnsupportedOperationException'.
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-11894
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11894
> Project: Cassandra
> Issue Type: Bug
> Components: Configuration
> Environment: Apache Cassandra 2.1.14.1272
> Reporter: Sucwinder Bassi
> Assignee: Yuki Morishita
> Priority: Minor
> Labels: JConsole
> Fix For: 2.1.x
>
> Attachments: jconsole_output.jpg
>
>
> When using JConsole to change the MaximumThreads from default 32 to 128 for
> ReadStage and MutationStage this exception is displayed
> 'java.lang.UnsupportedOperationException'. Nothing is written to the
> system.log.
> If I perform the same change using Apache Cassandra 2.0.8.39 I can change
> MaximumThreads to 128 for ReadStage and MutationStage without any problems.
> See the attached image showing the two machines.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
