[
https://issues.apache.org/jira/browse/HIVE-13086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15153179#comment-15153179
]
Prasanth Jayachandran commented on HIVE-13086:
----------------------------------------------
This is not related to SLF4J's runtime binding. This is just to avoid erroneous
autoconfiguration of logging for llap. [~gopalv]'s comment
https://issues.apache.org/jira/browse/HIVE-13027?focusedCommentId=15150141&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15150141
suspects logging initialized from some other properties files. If for some
reason logging is initialized with wrong properties file this initialization
(reconfiguration) will make sure llap always uses llap-daemon-log4j2.properties
file. Also it prints which file it picked up from classpath.
> LLAP: Programmatically initialize log4j2 to print out the properties location
> -----------------------------------------------------------------------------
>
> Key: HIVE-13086
> URL: https://issues.apache.org/jira/browse/HIVE-13086
> Project: Hive
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Prasanth Jayachandran
> Assignee: Prasanth Jayachandran
> Attachments: HIVE-13086.1.patch, HIVE-13086.2.patch
>
>
> In some cases, llap daemon gets initialized with different log4j2.properties
> than the expected llap-daemon-log4j2.properties. It will be easier if
> programmatically configure log4j2 so that we can print out the location of
> properties file that is used for initialization.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
