You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2019/02/07 11:00:04 UTC

[jira] [Commented] (AMBARI-24958) Ambari YARN Queue Manager allows duplicate names when using 'rename' functionality

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

Hudson commented on AMBARI-24958:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10458 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10458/])
AMBARI-24958 Ambari YARN Queue Manager allows duplicate names when using (m.magyar3: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=157eed41d264922dd0e6335dc4b54c53859a83a4])
* (edit) contrib/views/capacity-scheduler/src/main/resources/ui/app/controllers/queue.js


> Ambari YARN Queue Manager allows duplicate names when using 'rename' functionality
> ----------------------------------------------------------------------------------
>
>                 Key: AMBARI-24958
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24958
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.6.0
>            Reporter: Jonathan Sneep
>            Assignee: Akhil S Naik
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Using the rename functionality in Ambari YARN Queue Manager, it is possible to set multiple queues of the same name.
>  # On a new, empty cluster, create an "example" parent queue, and refresh YARN config
>  # Create another new parent queue named "MainExample"
>  # Add two leaf queues into "MainExample", but note that Ambari will indicate that a leaf queue named "example" cannot be created as a queue with that name already exists. Therefore we now call the new leaf queues "leaf1" and "leaf2" instead.
>  # The rename option will allow to rename the queue "leaf1" into "example" without any error (this is the bug, as it should give the same error as in step 3).
>  # Saving and attempting to use the configuration after these steps will result in RM failing with a variety of errors.
> We need logic in the Ambari YARN Queue Manager to verify new queues for duplicate queue names when using the rename function.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)