[
https://issues.apache.org/jira/browse/SOLR-9570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527573#comment-15527573
]
Shawn Heisey commented on SOLR-9570:
------------------------------------
bq. The file is useful since it will capture any errors happening outside of
the logging system
Good point, and I did not think of that.
If we'll always be attempting to mute log4j's CONSOLE output when in background
mode, perhaps we can let the console log grow, because it will not normally get
much output. Alternately we could rotate it through a simple fixed set of 10
filenames, changing a single 0-9 digit ... so there would be history for
several start attempts.
> Logs backed up on restart are kept forever
> ------------------------------------------
>
> Key: SOLR-9570
> URL: https://issues.apache.org/jira/browse/SOLR-9570
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Reporter: Jan Høydahl
>
> When (re)starting Solr, the start script will backup any existing
> {{solr.log}} or {{solr_gc.log}} to a file {{solr_log_<date>}} and
> {{solr_gc_log_<date>}} respectively. That may be all good, but these old
> copies are never cleaned up, as they are not under the control of log4j.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
