You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (Updated) (JIRA)" <ji...@apache.org> on 2012/02/27 22:43:48 UTC

[jira] [Updated] (CASSANDRA-3797) StorageProxy static initialization not triggered until thrift requests come in

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

Jonathan Ellis updated CASSANDRA-3797:
--------------------------------------

    Attachment: 3797-forname-this-time-for-sure.txt

correct forname patch attached.

figured out my problem from last time: I was looking for StorageProxy under the old location in o.a.c.service, instead of o.a.c.db.  It appears correctly on startup in o.a.c.db with this patch.
                
> StorageProxy static initialization not triggered until thrift requests come in
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-3797
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3797
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Peter Schuller
>            Assignee: Peter Schuller
>            Priority: Minor
>             Fix For: 1.1.0
>
>         Attachments: 3797-forname-this-time-for-sure.txt, 3797-forname.txt, CASSANDRA-3797-trunk-v1.txt
>
>
> While plugging in the metrics library for CASSANDRA-3671 I realized (because the metrics library was trying to add a shutdown hook on metric creation) that starting cassandra and simply shutting it down, causes StorageProxy to not be initialized until the drain shutdown hook.
> Effects:
> * StorageProxy mbean missing in visualvm/jconsole after initial startup (seriously, I thought I was going nuts ;))
> * And in general anything that makes assumptions about running early, or at least not during JVM shutdown, such as the metrics library, will be problematic

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira