[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514578#comment-15514578 ] Jan Høydahl commented on SOLR-8186: --- Documented auto console log muting in RefGuide: https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=32604193=24=23 > 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513194#comment-15513194 ] ASF subversion and git services commented on SOLR-8186: --- Commit 7498ca9ad67b25e48e2ae182256864b06d82e186 in lucene-solr's branch refs/heads/branch_6x from [~janhoy] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=7498ca9 ] SOLR-8186: Added robustness to the dynamic log muting logic (cherry picked from commit eabb05f) > 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[
https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513166#comment-15513166 ] Shawn Heisey commented on SOLR-8186: bq. Checks that log4j is actually bound by slf4j Would this mean that somebody who changes their logging jars on purpose gets a warning? Note that I am not actually opposed to assuming slf4j->log4j (and eventually log4j2) in what we incorporate into Solr, particularly as we move to making a standalone application. Taking away the user's choice of logging framework would allow us to control logging more effectively from the admin UI. > 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[
https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513068#comment-15513068
]
Jan Høydahl commented on SOLR-8186:
---
Regarding NoClassDefFoundError, we'll never get as far as calling any methods
on LogManager since we first check for the existence with Class.forName. But I
could change both catch clauses to catching {{Throwable}} to get both Errors
and Exceptions?
We still need CheckLoggingConfiguration as this new code is not always called,
and it does not exit on error, but continue running.
> 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513036#comment-15513036 ] ASF subversion and git services commented on SOLR-8186: --- Commit eabb05f7fd52e9e9946160101607052b14b2cfe2 in lucene-solr's branch refs/heads/master from [~janhoy] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=eabb05f ] SOLR-8186: Added robustness to the dynamic log muting logic > 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513035#comment-15513035 ] Uwe Schindler commented on SOLR-8186: - Small thing. I would also catch NoClassDefFoundError (or Errors in general). See CheckLoggingConfiguration. I am not 100% sure if CheckLoggingConfiguration is still used anywhere. Maybe nuke it! You code is a kind of duplicate. > 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513029#comment-15513029 ] Uwe Schindler commented on SOLR-8186: - +1 Thanks, Uwe > 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[
https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15512537#comment-15512537
]
Dawid Weiss commented on SOLR-8186:
---
No problem. I actually still can't get precommit to work, it fails with:
{code}
-documentation-lint:
[jtidy] Checking for broken html (such as invalid tags)...
[delete] Deleting directory
/mnt/storage/dweiss/work/lucene-solr/lucene/build/jtidy_tmp
[echo] Checking for broken links...
[exec]
[exec] Crawl/parse...
[exec]
[exec] Verify...
[exec]
[exec]
file:///mnt/storage/dweiss/work/lucene-solr/solr/build/docs/quickstart.html
[exec] BAD EXTERNAL LINK: http://lucene.apache.org/solr/downloads.html
[exec]
[exec] Broken javadocs links were found!
{code}
So you can make up and fix this one instead ;)
> 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, 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15512527#comment-15512527 ] Jan Høydahl commented on SOLR-8186: --- Thanks [~dawid.weiss] for stepping in on this - I obviously forgot to run ant precommit, sorry for breaking the build :-( When switching to Log4j2 we'll have to revisit the way of doing things as this method will no longer work, hopefully there is a "cleaner" way... > 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, 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15512507#comment-15512507 ] ASF subversion and git services commented on SOLR-8186: --- Commit 0a24afdc5b51fb0275a168ee502555bf06d91ff5 in lucene-solr's branch refs/heads/branch_6x from [~dawid.weiss] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=0a24afd ] SOLR-8186: suppress log4j access warnings. > 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, 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15512509#comment-15512509 ] ASF subversion and git services commented on SOLR-8186: --- Commit 9e09045a4c61a8d35b994adadd8f283add10cba7 in lucene-solr's branch refs/heads/master from [~dawid.weiss] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=9e09045 ] SOLR-8186: suppress log4j access warnings. > 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, 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15511535#comment-15511535 ] ASF subversion and git services commented on SOLR-8186: --- Commit dfb8aff7394057e132c3b3ca0ef107f280cca8df in lucene-solr's branch refs/heads/branch_6x from [~janhoy] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=dfb8aff ] SOLR-8186: Solr start scripts, only log to console when running in foreground > 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, 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15511501#comment-15511501 ] ASF subversion and git services commented on SOLR-8186: --- Commit 2ef34e9e24ac2c0bd72de54c3edda9ba3aa43728 in lucene-solr's branch refs/heads/master from [~janhoy] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=2ef34e9 ] SOLR-8186: Solr start scripts, only log to console when running in foreground > 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, 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506009#comment-15506009 ] Jan Høydahl commented on SOLR-8186: --- I intend to commit this in a few days if lazy consensus > 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, 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15505494#comment-15505494 ] Shawn Heisey commented on SOLR-8186: Cool. Thanks. I hadn't actually looked at the script, I was just thinking out loud. > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[
https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504976#comment-15504976
]
Jan Høydahl commented on SOLR-8186:
---
When in foreground mode, the CONSOLE logging goes to the console -
{{logs/solr-8983-console.log}} is NOT written. Try it :)
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504965#comment-15504965 ] Shawn Heisey commented on SOLR-8186: 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[
https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15504941#comment-15504941
]
Jan Høydahl commented on SOLR-8186:
---
The only output in {{solr-8983-console.log}} when starting in backgorund is now
these two lines:
{noformat}
2016-09-19 22:40:45.836 INFO (main) [ ] o.e.j.s.Server jetty-9.3.8.v20160314
2016-09-19 22:40:46.120 INFO (main) [ ] o.a.s.s.SolrDispatchFilter Property
solr.log.muteconsole=true. Muting log appender named "CONSOLE".
{noformat}
Please give it a spin and report your findings. I have not yet tested the
solr.cmd changes, anyone on Windows who wants to test?
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503720#comment-15503720 ] Erick Erickson commented on SOLR-8186: -- Agreed, having the timestamp as ticks in the console rather than a human-readable format is disconcerting, +1 to change it to the same format as the rest of the log files. bq: Do we even need to write to logs/solr.log. IMO absolutely we do. There is so much output that having the solr.log file is important to answer "what did I see go by?" when chasing down problems. > 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 > > 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[
https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15503539#comment-15503539
]
Jan Høydahl commented on SOLR-8186:
---
Is this still the case?
Do we even need to write to {{logs/solr.log}} when running in foreground mode?
If not, the {{log4j-foreground.properties}} could do CONSOLE only.
Also, why does the log format need to be different between console and file? I
know some Windows users start Solr with NSSM in foreground mode and relies on
NSSM to capture console logging and take care of persisting and rolling the
logs. You would expect to find a timestamp in those logs!
{noformat}
solr.log:
2016-09-19 13:42:46.607 INFO (main) [ ] o.e.j.u.log Logging initialized
@361ms
2016-09-19 13:42:46.772 INFO (main) [ ] o.e.j.s.Server jetty-9.3.8.v20160314
solr-8983-console.log:
0INFO (main) [ ] o.e.j.u.log Logging initialized @361ms
165 INFO (main) [ ] o.e.j.s.Server jetty-9.3.8.v20160314
{noformat}
> 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
>
> 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969247#comment-14969247 ] Shawn Heisey commented on SOLR-8186: The start script should continue to capture the console to a separate logfile when running in the background. That will capture startup errors and any stdout/stderr logging that Solr might do when debugging code changes. > 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 > > 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
[jira] [Commented] (SOLR-8186) Solr start scripts -- only log to console when running in foreground
[ https://issues.apache.org/jira/browse/SOLR-8186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14969263#comment-14969263 ] Erick Erickson commented on SOLR-8186: -- Yeah, it's surprising when your disk fills up! > 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 > > 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
