cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Or Sher (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7786) Cassandra is shutting down out of no apparent reason
Date Mon, 01 Sep 2014 09:07:20 GMT


Or Sher commented on CASSANDRA-7786:

I believe the problem is a linux implementaion/bug when a kill signal is sent by mistake to
another processes (In my case, to C* java process).

Although it would have save some investigation time if the killer process details were logged

> Cassandra is shutting down out of no apparent reason
> ----------------------------------------------------
>                 Key: CASSANDRA-7786
>                 URL:
>             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 (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 (line 141)
Stop listening to thrift clients
>  INFO [StorageServiceShutdownHook] 2014-08-15 01:40:59,007 (line 182) Stop
listening for CQL clients
>  INFO [StorageServiceShutdownHook] 2014-08-15 01:40:59,011 (line 1279)
Announcing shutdown
>  INFO [StorageServiceShutdownHook] 2014-08-15 01:41:01,011 (line
683) Waiting for messaging service to quiesce
>  INFO [ACCEPT-/] 2014-08-15 01:41:01,012 (line 923)
MessagingService has terminated the accept() thread
>  INFO [main] 2014-08-17 09:50:56,647 (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
> 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

View raw message