cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Resolved] (CASSANDRA-2359) Cassandra 0.7.4 seems to die
Date Mon, 21 Mar 2011 00:13:06 GMT


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

View raw message