cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.B. Langston (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-5037) Set CASSANDRA_HEAPDUMP_DIR in cassandra-env.sh by default
Date Thu, 06 Dec 2012 15:59:10 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

J.B. Langston updated CASSANDRA-5037:
-------------------------------------

    Description: 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 cassandra-env.sh, 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 written.
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. We should set it by default to e.g.
/var/log/cassandra.  (was: 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 cassandra-env.sh, 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 written. 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. We should set
it by default to, e.g. /var/log/cassandra.)
    
> Set CASSANDRA_HEAPDUMP_DIR in cassandra-env.sh by default
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-5037
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5037
>             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 cassandra-env.sh, 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 written.
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. 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: http://www.atlassian.com/software/jira

Mime
View raw message