cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Schuller (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3797) StorageProxy static initialization not triggered until thrift requests come in
Date Mon, 27 Feb 2012 20:10:46 GMT

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

Peter Schuller commented on CASSANDRA-3797:
-------------------------------------------

Looks like {{3797-forname.txt}} is the same file as the original patch. In any case, suppose
we just go for Class.forName() to avoid introducing that annoying method, and assuming it
makes the metrics from CASSANDRA-3671, can I get a +1?
                
> 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.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

        

Mime
View raw message