ambari-issues mailing list archives

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

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

Hudson commented on AMBARI-22033:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8186 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8186/])
AMBARI-22033. LLAP log level propagated incorrectly. (Prasanth (sshridhar: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=86afb7c1d8ad2f8367d12616abb06455c6449a2d])
* (edit) ambari-server/src/main/resources/stacks/HDP/2.5/services/HIVE/configuration/llap-daemon-log4j.xml


> 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