[
https://issues.apache.org/jira/browse/AMBARI-15048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147466#comment-15147466
]
Hadoop QA commented on AMBARI-15048:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12787946/AMBARI-15048.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5374//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5374//console
This message is automatically generated.
> ambari should make sure it uses only leaf queue name in configs
> ---------------------------------------------------------------
>
> Key: AMBARI-15048
> URL: https://issues.apache.org/jira/browse/AMBARI-15048
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.2.2
>
> Attachments: AMBARI-15048.patch, AMBARI-15048.patch
>
>
> I have a cluster where i have nested queues like hive.tpcds, hive.tpch etc.
> What i noticed when i added ranger to my cluster my hive configs changed for
> hive server2 default queue names to hive.tpcds etc. Fully qualified queue
> names do no work.
> Instead
> ambari should make sure it should queue names to just the leaf node like
> tpcds, tpch etc. In the CS view we probably also need to make sure that leaf
> queue names are unique.
> So after adding ranger HS2 service alerts started showing and HS2 died as it
> was referring to a queue that yarn does not resolve. So i had to revert the
> queue config change to only have leaf nodes. Thats how i had setup the cluster
> before
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
