Hi Jean,
I had the same problem, I removed the lines in /etc/init.d/cassandra template
(we use Chef to deploy) and now the HeapDumpPath is not overridden anymore.The
same goes for -XX:ErrorFile.
Best,
Romain
Le Mardi 4 octobre 2016 9h25, Jean Carlo a
écrit :
Yes, we did it.
So if th
Yes, we did it.
So if the parameter in cassandra-env.sh is used only if we have a OOM, what
is for the definition of
*-XX:HeapDumpPath=/var/lib/cassandra/java_1475461286.hprof
*in /etc/init.d/cassandra for?
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Tu
Have you restarted Cassandra after making changes in cassandra-env.sh?
Yabin
On Mon, Oct 3, 2016 at 7:44 AM, Jean Carlo
wrote:
> OK I got the response to one of my questions. In the script
> /etc/init.d/cassandra we set the path for the heap dump by default in the
> cassandra_home.
>
> Now the
OK I got the response to one of my questions. In the script
/etc/init.d/cassandra we set the path for the heap dump by default in the
cassandra_home.
Now the thing I don't understand is, why do the dumps are located by the
file set by /etc/init.d/cassandra and not by the conf file
cassandra-env.s
Hi
I see in the log of my node cassandra that the parameter -XX:HeapDumpPath
is charged two times.
INFO [main] 2016-10-03 04:21:29,941 CassandraDaemon.java:205 - JVM
Arguments: [-ea, -javaagent:/usr/share/cassandra/lib/jamm-0.3.0.jar,
-XX:+CMSClassUnloadingEnabled, -XX:+UseThreadPriorities,
-XX:
