ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-22033) LLAP log level propagated incorrectly
Date Mon, 02 Oct 2017 17:01:00 GMT

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

Prasanth Jayachandran commented on AMBARI-22033:
------------------------------------------------

Yes. The patch will still be required. To make the previous comment more clear,
Ambari passes log level from (llap_log_level) variable via command line option which will
get overridden by llap-daemon-log4j2.properties. So this patch is required to set llap_log_level
in llap-daemon-log4j2.properties file as well. 

> LLAP log level propagated incorrectly
> -------------------------------------
>
>                 Key: AMBARI-22033
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22033
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>         Attachments: AMBARI-22033.1.patch
>
>
> llap daemon log4j2 properties is using {{hive_log_level}} for log level replacement instead
of {{llap_log_level}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message