You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Shotaro Kamio (JIRA)" <ji...@apache.org> on 2012/11/14 07:02:12 UTC

[jira] [Created] (CASSANDRA-4962) JMX bean of StorageProxy is sometimes invisible

Shotaro Kamio created CASSANDRA-4962:
----------------------------------------

             Summary: 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.12, 1.0.7
            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

[jira] [Commented] (CASSANDRA-4962) JMX bean of StorageProxy is sometimes invisible

Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-4962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496905#comment-13496905 ] 

Brandon Williams commented on CASSANDRA-4962:
---------------------------------------------

It's not invisible so much as it doesn't exist until it's instantiated.  The same is true of a number of other mbeans, most notably HintedHandOffManager which will require two nodes to appear.
                
> 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

[jira] [Commented] (CASSANDRA-4962) JMX bean of StorageProxy is sometimes invisible

Posted by "Shotaro Kamio (JIRA)" <ji...@apache.org>.
    [ 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