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

ASF GitHub Bot commented on KYLIN-4859:
---------------------------------------

hit-lacus merged pull request #1537:
URL: https://github.com/apache/kylin/pull/1537


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


> Log4J reinitialized/reconfigured by Spark Logging
> -------------------------------------------------
>
>                 Key: KYLIN-4859
>                 URL: https://issues.apache.org/jira/browse/KYLIN-4859
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Others
>    Affects Versions: v4.0.0-alpha
>            Reporter: ShengJun Zheng
>            Priority: Minor
>
> Spark Logging was intrucoded in kylin 4.0-alpha, it uses SL4J too, but it 
> will reinitialize log4j when RootLoggers's Appender is empty.
> See: 
> https://github.com/apache/spark/blob/45e19bb99acd5066723fec2bbdc0c99c696c3daf/core/src/main/scala/org/apache/spark/internal/Logging.scala#L120
> this causes some logs of a query logged in file(kylin.log), the other logged 
> in stdout(kylin.out) using configuration file log4j-defaults.properties in 
> spark-core_2.11-2.x.x.jar
> not firendly to read and anlyze a query performance, and may cause other 
> logging confusions
> To Avoid this is,  default appenders for rootLoggers should be set in 
> kylin-server-log4j.properties



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to