cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5037) Set CASSANDRA_HEAPDUMP_DIR in by default
Date Thu, 21 Mar 2013 16:43:15 GMT


Brandon Williams commented on CASSANDRA-5037:

bq. FTR I still think setting it to /tmp by default is reasonable.

I'm not.  People are going to run /tmp in one or two ways, generally.  a) it's a tiny mount
and not going to be big enough for a dump, or b) it's just part of the root and we're back
to the original problem.
> Set CASSANDRA_HEAPDUMP_DIR in by default
> ---------------------------------------------------------
>                 Key: CASSANDRA-5037
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Config
>    Affects Versions: 1.1.7, 1.2.0 beta 3
>            Reporter: J.B. Langston
>            Priority: Minor
> Cassandra is configured via -XX:+HeapDumpOnOutOfMemoryError to trigger a heap dump at
the occurrence of an OutOfMemoryError, but unless you have set your CASSANDRA_HEAPDUMP_DIR
in, the file will be written in the Cassandra process's working directory,
which when Cassandra is run as a service is typically the root directory. Nine times out of
ten, the Cassandra process does not have permission to write here so no heap dump is created.
Even if Cassandra does have permission, the root filesystem is usually small and the heap
dump could easily fill it up with a large Xmx configured. This makes post-mortem analysis
difficult. We should set it by default to e.g. /var/log/cassandra.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message