cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11894) Changing MaximumThreads for ReadStage and MutationStage using JConsole returns 'java.lang.UnsupportedOperationException'.
Date Tue, 20 Sep 2016 20:14:20 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Joshua McKenzie updated CASSANDRA-11894:
----------------------------------------
    Assignee: Yuki Morishita

> 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, 3.0.x, 3.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)

Mime
View raw message