hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gopal V (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-13086) LLAP: Programmatically initialize log4j2 to print out the properties location
Date Fri, 19 Feb 2016 07:22:18 GMT

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

Gopal V commented on HIVE-13086:
--------------------------------

LGTM - +1, tests pending.

{code}
2016-02-19T02:17:27,792 INFO  [main[]]: impl.LlapDaemon (LlapDaemon.java:initializeLogging(219))
- LLAP daemon logging initialized from file:/grid/4/hadoop/yarn/local/usercache/gopal/appcache/application_1455662455106_0226/container_e14_1455662455106_0226_01_000002/app/install/conf/llap-daemon-log4j2.properties
in 22 ms
{code}

> 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)

Mime
View raw message