default gc log settings overwrite previous log
-----------------------------------------------
Key: CASSANDRA-2418
URL: https://issues.apache.org/jira/browse/CASSANDRA-2418
Project: Cassandra
Issue Type: Bug
Affects Versions: 0.7.1
Reporter: Chris Burroughs
Priority: Minor
For those spoiled by nice rolling and appending syslogs log4js etc the JVM gc
log can be jarring:
{{
# GC logging options -- uncomment to enable
# JVM_OPTS="$JVM_OPTS -XX:+PrintGCDetails"
# JVM_OPTS="$JVM_OPTS -XX:+PrintGCTimeStamps"
# JVM_OPTS="$JVM_OPTS -XX:+PrintClassHistogram"
# JVM_OPTS="$JVM_OPTS -XX:+PrintTenuringDistribution"
# JVM_OPTS="$JVM_OPTS -XX:+PrintGCApplicationStoppedTime"
# JVM_OPTS="$JVM_OPTS -Xloggc:/var/log/cassandra/gc.log"
}}
Will result in gc.log with days of data being overwritten on restart, which
leads to sad faces.
The simplest change would be along these lines:
{{
GC_LOG_TS=`date +%s`
JVM_OPTS="$JVM_OPTS -XX:+PrintGCDetails"
JVM_OPTS="$JVM_OPTS -XX:+PrintGCTimeStamps"
JVM_OPTS="$JVM_OPTS -XX:+PrintClassHistogram"
JVM_OPTS="$JVM_OPTS -XX:+PrintTenuringDistribution"
JVM_OPTS="$JVM_OPTS -XX:+PrintGCApplicationStoppedTime"
JVM_OPTS="$JVM_OPTS -Xloggc:log/gc-$GC_LOG_TS.log"
}}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
