[
https://issues.apache.org/jira/browse/CASSANDRA-7786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benedict resolved CASSANDRA-7786.
---------------------------------
Resolution: Not a Problem
I agree it would be helpful to log that the process received a kill signal,
however this is not trivial to achieve in Java. If you want to submit a patch,
feel free to file a ticket and attach it there. Closing this as Not a Problem
> Cassandra is shutting down out of no apparent reason
> ----------------------------------------------------
>
> Key: CASSANDRA-7786
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7786
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: C* 2.0.9
> Reporter: Or Sher
>
> We've recently start facing an issue when one of the C* node in our dev and
> CI cluster (Thanks god didn't happen yet in Prod) is shutting down from time
> to time without any exceptions or errors.
> There is usually something like that in the logs:
> INFO [MemoryMeter:1] 2014-08-15 01:32:43,266 Memtable.java (line 481)
> CFS(Keyspace='system', ColumnFamily='sstable_activity') liveRatio is
> 14.597030881851438 (just-counted was 14.596825396825396). calculation took
> 2ms for 84 cells
> INFO [StorageServiceShutdownHook] 2014-08-15 01:40:58,954 ThriftServer.java
> (line 141) Stop listening to thrift clients
> INFO [StorageServiceShutdownHook] 2014-08-15 01:40:59,007 Server.java (line
> 182) Stop listening for CQL clients
> INFO [StorageServiceShutdownHook] 2014-08-15 01:40:59,011 Gossiper.java
> (line 1279) Announcing shutdown
> INFO [StorageServiceShutdownHook] 2014-08-15 01:41:01,011
> MessagingService.java (line 683) Waiting for messaging service to quiesce
> INFO [ACCEPT-/192.168.27.241] 2014-08-15 01:41:01,012 MessagingService.java
> (line 923) MessagingService has terminated the accept() thread
> INFO [main] 2014-08-17 09:50:56,647 CassandraDaemon.java (line 135) Logging
> initialized
> You can see the last line in the log is usually written at least 5 minutes
> before the shutdown, sometimes 30 minutes before.
> I can't reproduce it as I have know idea why is that happening and how the
> attack this issue.
> I believe I'm not the only one suffering from this issue as there was a
> thread about such behavior in the user mail distribution.
> Any thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
