You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/02/17 15:46:24 UTC
[jira] Resolved: (CASSANDRA-2180) Cassandra node should log in
system.log how and when it was signalled to stop and when it stopped and if
it stopped without problems
[ https://issues.apache.org/jira/browse/CASSANDRA-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-2180.
---------------------------------------
Resolution: Invalid
Cassandra is crash-only. See http://www.usenix.org/events/hotos03/tech/candea.html for background.
> Cassandra node should log in system.log how and when it was signalled to stop and when it stopped and if it stopped without problems
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-2180
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2180
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.7.1
> Environment: Linux
> Reporter: Mateusz Korniak
> Priority: Minor
>
> During start we see:
> INFO [main] 2011-02-17 10:47:46,754 AbstractCassandraDaemon.java (line 77) Logging initialized
> But during stopping node via kill -TERM node.pid last message in logs we see:
> INFO [Thread-3] 2011-02-17 10:49:22,290 CassandraDaemon.java (line 153) Listening for thrift clients...
> Information when cassandra node was closed gracefully (signalled) and if whole process went smooth would be nice there.
> TIA
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira