[
https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15504965#comment-15504965
]
Shawn Heisey edited comment on SOLR-8186 at 9/19/16 11:06 PM:
--------------------------------------------------------------
I like it! The console logfile is a persistent thorn when disk space is
limited.
I understand the desire to log to the actual console in foreground mode, but
I'm not sure that we want to copy that output to a file in foreground mode,
especially if we are still creating solr.log. I think logging to solr.log even
in foreground mode is a good idea.
was (Author: elyograg):
I like it! The console logfile is a persistent thorn when disk space is
limited.
I understand the desire to log to the actual console in foreground mode, but
I'm not sure that we want to copy that output to a file, especially if we are
still creating solr.log. I think logging to solr.log even in foreground mode
is a good idea.
> Solr start scripts -- only log to console when running in foreground
> --------------------------------------------------------------------
>
> Key: SOLR-8186
> URL: https://issues.apache.org/jira/browse/SOLR-8186
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Affects Versions: 5.3.1
> Reporter: Shawn Heisey
> Assignee: Jan Høydahl
> Labels: logging
> Fix For: 6.3, master (7.0)
>
> Attachments: SOLR-8186.patch
>
>
> Currently the log4j.properties file logs to the console, and the start
> scripts capture console output to a logfile that never rotates. This can
> fill up the disk, and when the logfile is removed, the user might be alarmed
> by the way their memory statistics behave -- the "cached" memory might have a
> sudden and very large drop, making it appear to a novice that the huge
> logfile was hogging their memory.
> The logfile created by log4j is rotated when it gets big enough, so that
> logfile is unlikely to fill up the disk.
> I propose that we copy the current log4j.properties file to something like
> log4j-foreground.properties, remove CONSOLE logging in the log4j.properties
> file, and have the start script use the alternate config file when running in
> the foreground. This way users will see the logging output when running in
> the foreground, but it will be absent when running normally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
