cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shotaro Kamio (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4962) JMX bean of StorageProxy is sometimes invisible
Date Mon, 03 Dec 2012 05:43:58 GMT

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

Shotaro Kamio commented on CASSANDRA-4962:
------------------------------------------

Is it possible to make them (at least StorageProxy) instantiated at startup?
We'd like to confirm some parameters via jmx right after maintenance of cassandra instance.
But sending requests to cassandra is not what operators want to do in normal maintenance...

                
> JMX bean of StorageProxy is sometimes invisible
> -----------------------------------------------
>
>                 Key: CASSANDRA-4962
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4962
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.7, 1.0.12
>            Reporter: Shotaro Kamio
>
> StorageProxy exposes info via JMX bean "org.apache.cassandra.db:type=StorageProxy". But
that bean is sometimes invisible via jmxterm nor jconsole.
> Seems like it becomes visible after data comes in.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message