[
https://issues.apache.org/jira/browse/SOLR-8232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl resolved SOLR-8232.
-------------------------------
Resolution: Not A Problem
Now that we mute CONSOLE appenders when running in bg, the console log file
becomes almost empty, so the risk of it filling up during a run is now almost
nonexistent. On each restart a new file is started, and in SOLR-9570 I propose
to delete the oldest of those.
I'm resolving this as "Not a problem" for now. If you believe that stdout/err
logging during a single run still should rotate its log file automatically
(which requires something else than redirect) then please re-open and continue
work on this issue.
> bin/solr does not rotate console log file
> -----------------------------------------
>
> Key: SOLR-8232
> URL: https://issues.apache.org/jira/browse/SOLR-8232
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools
> Affects Versions: 5.3
> Reporter: Upayavira
> Priority: Minor
>
> The bin/solr script, when started with bin/solr start, uses this command to
> start Solr:
> {code} nohup "$JAVA" "${SOLR_START_OPTS[@]}" $SOLR_ADDL_ARGS -jar start.jar \
> "-XX:OnOutOfMemoryError=$SOLR_TIP/bin/oom_solr.sh $SOLR_PORT
> $SOLR_LOGS_DIR" "${SOLR_JETTY_CONFIG[@]}" \
> 1>"$SOLR_LOGS_DIR/solr-$SOLR_PORT-console.log" 2>&1 & echo $! >
> "$SOLR_PID_DIR/solr-$SOLR_PORT.pid"
> {code}
> This sends console output to stdout, with no means of rotating the log file,
> meaning it will eventually fill the drive unless restarted.
> I would propose that stdout be written to dev/null and we use proper means
> for handling logging, which can do proper log rotation as configured by the
> user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
