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

T Jake Luciani commented on CASSANDRA-3302:
-------------------------------------------

Jackson is this still happening? Or is it ok to close?
                
> stop Cassandra result in hang
> -----------------------------
>
>                 Key: CASSANDRA-3302
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3302
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>            Reporter: Jackson Chung
>            Assignee: T Jake Luciani
>             Fix For: 1.0.1
>
>
> testing this under trunk via a hacked package (replacing jars from 0.8.6 deb 
> installation)
> When calling service cassandra stop, the Cassandra process hang:
> http://aep.appspot.com/display/i6aIUCkt4kz0HG5l2VszMM7QvLo/
> The following logs is observed in the C* log:
>  INFO [main] 2011-10-03 23:20:46,434 AbstractCassandraDaemon.java (line 270) 
> Cassandra shutting down...
>  INFO [main] 2011-10-03 23:20:46,434 CassandraDaemon.java (line 218) Stop 
> listening to thrift clients
> Re-run this using 1.0.0 branch, (following the same "hack" procedure), C* 
> stop properly, and the following is observed in the log:
>  INFO [main] 2011-10-04 05:02:08,048 AbstractCassandraDaemon.java (line 270) 
> Cassandra shutting down...
>  INFO [main] 2011-10-04 05:02:08,049 CassandraDaemon.java (line 218) Stop 
> listening to thrift clients
>  INFO [Thread-2] 2011-10-04 05:02:08,318 MessagingService.java (line 482) 
> Shutting down MessageService...
>  INFO [Thread-2] 2011-10-04 05:02:08,319 MessagingService.java (line 497) 
> Waiting for in-progress requests to complete
>  INFO [ACCEPT-/10.83.77.171] 2011-10-04 05:02:08,319 MessagingService.java 
> (line 637) MessagingService shutting down server thread.
> could this be related to CASSANDRA-3261 ?

--
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

        

Reply via email to