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

David Smiley commented on SOLR-4129:
------------------------------------

bq. I would like to have short logs saying that each core has been started and 
that Solr is fully started. Would it be reasonable to file a jira asking for 
this to happen at WARN, or would I just have to figure out which class(es) to 
set to INFO in my log4j config?

Using WARN for an informational message just seems wrong to me, albeit I've 
seen it in some projects at work.  Simply setting only one class to INFO and 
others higher (e.g. WARN) wouldn't work because this would probably go in 
SolrCore which has plenty of other INFO messages to say.  Too much IMO.  I 
think the right solution is to log an announcement message to a special name 
like "org.apache.solr.announcement".  Yeah, file an issue for that.
                
> Solr doesn't support log4j 
> ---------------------------
>
>                 Key: SOLR-4129
>                 URL: https://issues.apache.org/jira/browse/SOLR-4129
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.0-ALPHA, 4.0-BETA, 4.0
>            Reporter: Raintung Li
>              Labels: log
>             Fix For: 4.1, 5.0
>
>         Attachments: patch-4129.txt
>
>
> For many project use the log4j, actually solr use slf logger framework, slf 
> can easy to integrate with log4j by design. 
> Solr use log4j-over-slf.jar to handle log4j case.
> This jar has some issues.
> a. Actually last invoke slf to print the logger (For solr it is 
> JDK14.logging).
> b. Not implement all log4j function. ex. Logger.setLevel() 
> c. JDK14 log miss some function, ex. thread.info, day rolling 
> Some dependence project had been used log4j that the customer still want to 
> use it. JDK14 log has many different with Log4j, at least configuration file 
> can't reuse.
> The bad thing is log4j-over-slf.jar conflict with log4j. If use solr, the 
> other project have to remove log4j.
> I think it shouldn't use log4j-over-slf.jar, still reuse log4j if customer 
> want to use it.

--
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: http://www.atlassian.com/software/jira

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

Reply via email to