[
https://issues.apache.org/jira/browse/YARN-9681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903174#comment-16903174
]
ANANDA G B commented on YARN-9681:
----------------------------------
Hi Eric Payne, In YARN 5788.
*Actual*
Am limit in scheduler UI is still based on old resource.
*Expected*
AM limit to be updated based new partition resource.
This is fine.
In current Jira:
*Actual:*
_*After running the job*_ on queue1 of pool1, then queue1 of DEFAULT_PARTITIONs
AM resource limit is setting based on the *effective capacity* of queue1 of
_*pool1*_.
*Expected*
Even after running the job on queue1 of pool1, then queue1 of
DEFAULT_PARTITIONs AM resource limit must be set based on the *effective
capacity* of queue1 of _*DEFAULT_PARTITION*s_.
> AM resource limit is incorrect for queue
> ----------------------------------------
>
> Key: YARN-9681
> URL: https://issues.apache.org/jira/browse/YARN-9681
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 3.1.1, 3.1.2
> Reporter: ANANDA G B
> Assignee: ANANDA G B
> Priority: Major
> Labels: patch
> Attachments: After running job on queue1.png, Before running job on
> queue1.png, YARN-9681.0001.patch, YARN-9681.0002.patch, YARN-9681.0003.patch,
> YARN-9681.0004.patch
>
>
> After running the job on Queue1 of Partition1, then Queue1 of
> DEFAULT_PARTITION's 'Max Application Master Resources' is calculated wrongly.
> Please find the attachement.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
