[
https://issues.apache.org/jira/browse/AMBARI-15048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15158788#comment-15158788
]
Hudson commented on AMBARI-15048:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #4372 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4372/])
AMBARI-15048. ambari should make sure it uses only leaf queue name in
(aonishuk:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=396b7da71b18a837416b67e6b8a29cde62265709])
* ambari-server/src/test/python/stacks/2.2/common/test_stack_advisor.py
*
ambari-server/src/main/resources/stacks/HDPWIN/2.2/services/HIVE/configuration/hive-site.xml
* ambari-server/src/main/resources/stacks/HDP/2.2/services/stack_advisor.py
* ambari-server/src/main/resources/stacks/HDPWIN/2.2/services/stack_advisor.py
> 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
>
>
> 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)
