[CASSANDRA-2418] default gc log settings overwrite previous log

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 0.7.5
• Severity: Low
• Assignee: Chris Burroughs
• Reporter: Chris Burroughs

Authors

Chris Burroughs

Reviewers

Jonathan Ellis

• Created: 05/Apr/11 20:16
• Updated: 16/Apr/19 09:33
• Resolved: 07/Apr/11 15:54

Description

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:/var/log/cassandra/gc-$GC_LOG_TS.log"

There are probably prettier approaches.