[
https://issues.apache.org/jira/browse/YARN-11513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17732934#comment-17732934
]
ASF GitHub Bot commented on YARN-11513:
---------------------------------------
susheel-gupta commented on PR #5748:
URL: https://github.com/apache/hadoop/pull/5748#issuecomment-1592630665
> Thanks @susheel-gupta for the patch. I'm wondering: is there a way to
unittest this issue? There are some recovery related tests, i.e in
TestWorkPreservingRMRestart, where this might be reproducible. That way it's a
bit easier to verify this change.
Sure, I'll check TestWorkPreservingRMRestart testcases and try to add unit
test for this fix.
> Applications submitted to ambiguous queue fail during recovery if "Specified"
> Placement Rule is used
> ----------------------------------------------------------------------------------------------------
>
> Key: YARN-11513
> URL: https://issues.apache.org/jira/browse/YARN-11513
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
> Affects Versions: 3.3.4
> Reporter: Susheel Gupta
> Assignee: Susheel Gupta
> Priority: Major
> Labels: pull-request-available
>
> When an app is submitted to an ambiguous queue using the full queue path and
> is placed in that pool via a {{%specified}} mapping Placement Rule, the queue
> in the stored ApplicationSubmissionContext will be the short name for the
> queue. During recovery from an RM failover, the placement rule will be
> evaluated using the stored short name of the queue, resulting in the RM
> killing the app as it cannot resolve the ambiguous queue name.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
