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

Lyuben Todorov updated CASSANDRA-4268:
--------------------------------------

    Attachment: 4268-cassandra-2.0_v2.patch

Added a System.exit(0) to SS#stopDaemon and switched to using 
CassandraDaemon#deactivate (calls both {{stop()}} and {{destroy()}}). Because 
cassandra is shutting down, an exception is displayed in the nodetool, instead 
of displaying the exception (which isn't a problem as we are shutting C* down) 
it's caught and a "Cassandra has shut down" message is displayed. 

> Expose full stop() operation through JMX
> ----------------------------------------
>
>                 Key: CASSANDRA-4268
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4268
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Tyler Hobbs
>            Assignee: Lyuben Todorov
>            Priority: Minor
>              Labels: jmx
>             Fix For: 2.0.5
>
>         Attachments: 4268-cassandra-2.0_v2.patch, 4268_cassandra-2.0.patch
>
>
> We already expose ways to stop just the RPC server or gossip.  This would 
> fully shutdown the process.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to