cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3056) Able to set path location of HeapDump in cassandra-env
Date Mon, 29 Aug 2011 19:15:38 GMT


Eric Evans commented on CASSANDRA-3056:
--------------------------------------- is used to setup the "environment", (the jvm and everything that is passed
to it); cassandra.yaml is really the wrong place for this.  But, I agree with Jonathan that
it doesn't seem right to add to the list of first-start criteria, particularly
for something that only a small fraction of users will be concerned with.

Why not make this env-only?  If CASSANDRA_HEAP_DUMP_PATH (or whatever) is set, then use it
to construct the argument (from

> Able to set path location of HeapDump in cassandra-env
> ------------------------------------------------------
>                 Key: CASSANDRA-3056
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 0.7.8, 0.8.4
>            Reporter: David Talbott
>            Priority: Minor
>              Labels: lhf
>         Attachments: CASSANDRA-3056-1.txt, CASSANDRA-3056-2.txt
> We should be able to designate the path location to put any perf dumps that are performed.
By Default with this not set the perf dump can occur on the root disk and fill the drive.

> Should be able to solve this by simply inserting JVM_OPTS="$JVM_OPTS -XX:HeapDumpPath=<path
to dir>" into as a default option available and set. 

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message