Jan Høydahl commented on SOLR-9534:

The {{-q}} flag logs with WARN level. With this patch, it will produce this for 
{{bin/solr start -f -q}}

Starting Solr on port 8983 from /Users/janhoy/git/lucene-solr/solr/server

0    INFO  (main) [   ] o.e.j.s.Server jetty-9.3.8.v20160314
198  WARN  (main) [   ] o.e.j.s.SecurityHandler 
 has uncovered http methods for path: /
205  INFO  (main) [   ] o.a.s.s.SolrDispatchFilter Log level override, property 
298  WARN  (main) [   ] o.a.s.c.CoreContainer Couldn't add files from 
/Users/janhoy/git/lucene-solr/solr/server/solr/lib to classpath: 
553  INFO  (main) [   ] o.e.j.s.h.ContextHandler Started 
566  INFO  (main) [   ] o.e.j.s.ServerConnector Started 
567  INFO  (main) [   ] o.e.j.s.Server Started @986ms

PS: The two WARN logs are removed over in SOLR-8186, as well as printing 
date&time in console log.

A problem with just switching to WARN is that we pretty much mute everything 
Solr has to say :) The easiest solution is to explicitly set log level to INFO 
for a few selected Solr classes which we still want to see. Or long term 
implement the ideas from SOLR-4132 

> Support quiet/verbose bin/solr options for changing log level
> -------------------------------------------------------------
>                 Key: SOLR-9534
>                 URL: https://issues.apache.org/jira/browse/SOLR-9534
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: scripts and tools
>    Affects Versions: 6.2
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>              Labels: logging
>             Fix For: 6.3, master (7.0)
>         Attachments: SOLR-9534.patch
> Spinoff from SOLR-6677
> Let's make it much easier to "turn on debug" by supporting a {{bin/solr start 
> -V}} verbose option, and likewise a {{bin/solr start -q}} for quiet operation.
> These would simply be convenience options for changing the RootLogger from 
> level INFO to DEBUG or WARN respectively. This can be done programmatically 
> in log4j at startup. 
> Could be we need to add some more package specific defaults in 
> log4j.properties to get the right mix of logs

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to