[
https://issues.apache.org/jira/browse/CASSANDRA-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017029#comment-13017029
]
Hudson commented on CASSANDRA-2418:
-----------------------------------
Integrated in Cassandra-0.7 #424 (See
[https://hudson.apache.org/hudson/job/Cassandra-0.7/424/])
add date in seconds-since-epoch to default gc log filename
patch by Chris Burroughs and jbellis for CASSANDRA-2418
> 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
> Assignee: Chris Burroughs
> Priority: Minor
> Fix For: 0.7.5
>
> Attachments: 2418.txt
>
>
> For those spoiled by nice rolling and appending syslogs log4js etc the JVM gc
> log can be jarring:
> {noformat}
> # 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"
> {noformat}
> 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:
> {noformat}
> 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"
> {noformat}
> There are probably prettier approaches.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
