[
https://issues.apache.org/jira/browse/CASSANDRA-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-2359.
---------------------------------------
Resolution: Invalid
Dying Cassandra is either an OutOfMemoryError or a JVM crash. The former will
yield a heap dump; the latter will create a crash log file. This may be in the
directory you started Cassandra in or in /, depending on the script you used to
start it and assuming the Cassandra process has permission to write to that
directory.
Neither of these is a Cassandra bug.
(OOME will also be logged to the system.log; fixing that should be your first
priority.)
> Cassandra 0.7.4 seems to die
> ----------------------------
>
> Key: CASSANDRA-2359
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2359
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.4
> Environment: MacOs X
> Reporter: Olivier Smadja
> Priority: Critical
>
> After migrating from Cassandra 0.7.2 to 0.7.4 the Cassandra server seems to
> shutdown alone quietly.
> This situation occurred 3 times in one week, my Cassandra server was up and
> without killing it, it suddenly shutdown.
> For some reason, my system.log file is not being updated :-(
> My log4j-server.properties contains the following line:
> log4j.appender.R.File=/Users/olivier/Data/Cassandra/data/system-cassandra.log
> but the file there is not updated....
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
