[ 
https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15513189#comment-15513189
 ] 

Jan Høydahl commented on SOLR-8186:
-----------------------------------

Yes, they will get a warning when running in {{solr-8983-console.log}} that we 
were not able to tune down logging.
But then again, if they actually switched to Logback or some other backend, 
then they are on their own in configuring that framework, and they may not even 
configure any Console loggers at all, so then it is not really a problem that 
we were unable to mute log4j ConsoleAppenders...

+1 to choosing one log backend and not officially support anything else.

> 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-robustness.patch, SOLR-8186.patch, 
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to