[
https://issues.apache.org/jira/browse/SOLR-8232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994254#comment-14994254
]
Erick Erickson commented on SOLR-8232:
--------------------------------------
[~arafalov] Your point about poorly-behaved messages (i.e. not going through
logging) being lost is well taken, but what do you think should be done in that
case to not blow up disk space by recording all console output?
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
