[
https://issues.apache.org/jira/browse/YARN-11662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ferenc Erdelyi resolved YARN-11662.
-----------------------------------
Resolution: Duplicate
Duplicate of YARN-11538
> RM Web API endpoint queue reference differs from JMX endpoint for CS
> --------------------------------------------------------------------
>
> Key: YARN-11662
> URL: https://issues.apache.org/jira/browse/YARN-11662
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 3.4.0
> Reporter: Ferenc Erdelyi
> Assignee: Ferenc Erdelyi
> Priority: Major
>
> When a placement is not successful (because of the lack of a placement rule
> or an unsuccessful placement), the application is placed in the default queue
> instead of the root.default. The parent queue won't be defined when there is
> no placement rule. This causes an inconsistency between the JMX endpoint
> (reporting the app. runs under the root.default) and the RM Web API endpoint
> (reporting the app runs under the default queue).
> Similarly, when we submit an application with an unambiguous leaf queue
> specified, the RM Web API endpoint will report the queue as the leaf queue
> name instead of the full queue path. However, the full queue path is the
> expected value to be consistent with the JMX endpoint.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
