[ https://issues.apache.org/jira/browse/SOLR-9815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728630#comment-15728630 ]
Gethin James commented on SOLR-9815: ------------------------------------ A work around for windows is {code}set "GC_LOG_OPTS= "{code} The relavant logic from solr/bin/solr: {code} # Establish default opts no env var set (otherwise init to empty) if [ -z ${GC_LOG_OPTS+x} ]; then GC_LOG_OPTS=('-verbose:gc' '-XX:+PrintHeapAtGC' '-XX:+PrintGCDetails' \ '-XX:+PrintGCDateStamps' '-XX:+PrintGCTimeStamps' '-XX:+PrintTenuringDistribution' \ '-XX:+PrintGCApplicationStoppedTime') else GC_LOG_OPTS=($GC_LOG_OPTS) fi # if verbose gc logging enabled, setup the location of the log file and rotation if [ "$GC_LOG_OPTS" != "" ]; then gc_log_flag="-Xloggc" if [ "$JAVA_VENDOR" == "IBM J9" ]; then gc_log_flag="-Xverbosegclog" fi GC_LOG_OPTS+=("$gc_log_flag:$SOLR_LOGS_DIR/solr_gc.log" -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M) fi {code} and from solr.cmd: {code} IF "%GC_LOG_OPTS%"=="" ( set GC_LOG_OPTS=-verbose:gc ^ -XX:+PrintHeapAtGC ^ -XX:+PrintGCDetails ^ -XX:+PrintGCDateStamps ^ -XX:+PrintGCTimeStamps ^ -XX:+PrintTenuringDistribution ^ -XX:+PrintGCApplicationStoppedTime ) {code} [~janhoy] Was the plan to keep verbose garbage collection logging on by default? > Verbose Garbage Collection logging is on by default > --------------------------------------------------- > > Key: SOLR-9815 > URL: https://issues.apache.org/jira/browse/SOLR-9815 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: logging > Affects Versions: 6.3 > Reporter: Gethin James > Priority: Minor > > There have been some excellent logging fixes in 6.3 > (http://www.cominvent.com/2016/11/07/solr-logging-just-got-better/). However > now, by default, Solr is logging a great deal of garbage collection > information. > It seems that this logging is excessive, can we make the default logging to > not be verbose? > For linux/mac setting GC_LOG_OPTS="" in solr.in.sh seems to work around the > issue, but looking at solr.cmd I don't think that will work for windows. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org