[SOLR-9971] Parameterise where solr creates its console and gc log files

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 6.3
• Component/s: scripts and tools
• Labels: newbie
• Assignee: Unassigned
• Reporter: Jinesh Choksi
• Created: 16/Jan/17 18:13
• Updated: 08/Jun/19 15:32

Description

In the $SOLR_INSTALL_DIR/bin/solr script, the location where the solr_gc.log + $SOLR_PORT-console.log file are created is hard wired to be inside the $SOLR_LOGS_DIR folder due to the following lines of code:

• GC_LOG_OPTS+=("$gc_log_flag:$SOLR_LOGS_DIR/solr_gc.log" -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=9 -XX:GCLogFileSize=20M)
  

• nohup "$JAVA" "${SOLR_START_OPTS[@]}" $SOLR_ADDL_ARGS -Dsolr.log.muteconsole \
  	"-XX:OnOutOfMemoryError=$SOLR_TIP/bin/oom_solr.sh $SOLR_PORT $SOLR_LOGS_DIR" \
          -jar start.jar "${SOLR_JETTY_CONFIG[@]}" \
  	1>"$SOLR_LOGS_DIR/solr-$SOLR_PORT-console.log" 2>&1 & echo $! > "$SOLR_PID_DIR/solr-$SOLR_PORT.pid"
  

Would it be possible to arrange for another two ENVIRONMENT variables to be made available which allow us to control where these two files are created?

e.g. SOLR_GC_LOG + SOLR_CONSOLE_LOG

The use case behind this request is that it is useful to keep gc and console logs separate from the application logs because there are different archival / ingestion / processing requirements for each.

Issue Links

• is related to: SOLR-11233 GC_LOG_OPTS customisation is a little confusing

Sub-Tasks

• Parameterise where solr creates its gc log files: Open