lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <>
Subject [jira] [Created] (SOLR-3979) slf4j bindings other than jdk -- cannot change log levels
Date Tue, 23 Oct 2012 13:49:11 GMT
Shawn Heisey created SOLR-3979:

             Summary: slf4j bindings other than jdk -- cannot change log levels
                 Key: SOLR-3979
             Project: Solr
          Issue Type: Bug
    Affects Versions: 4.0
            Reporter: Shawn Heisey
             Fix For: 4.1

Once I finally got log4j logging working, I was slightly surprised by the message related
to SOLR-3426.  I did not really consider that to be a big deal, because if I want to look
at my log, I'll be on the commandline anyway.

I was even more surprised to find that I cannot change any of the log levels from the admin
gui.  My default log level is WARN for performance reasons, but every once in a while I like
to bump the log level to INFO to troubleshoot a specific problem, then turn it back down.
 This is very easy with jdk logging in either 3.x or 4.0.  I changed to log4j because it easily
allows me to put the date of a log message on the same line as the first line of the actual
log message, so when I grep for things, I have the timestamp in the grep output.

Currently the only way for me to change my log level is by updating and restarting
Solr.  If the capability to figure this out on a class-by-class basis isn't there with log4j,
I would at least like to be able to set the root logging level.  Is that possible?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message