[
https://issues.apache.org/jira/browse/YARN-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075380#comment-15075380
]
Wangda Tan commented on YARN-4495:
----------------------------------
Thanks for investigations, [~sandflee].
I feel we should make this JIRA to be more generic helpful:
- Current any issue of regular resource request becomes
InvalidResourceRequestException, but AM doesn't know which resource request is
failed. Similar to change container resource request.
- Some resource request / change container resource request could be rejected
after it added to scheduler. (For example, queue's accessible-node-label
changed could cause some original valid resource request changes to invalid.)
- Maybe we can add a "RejectedResourceRequest" proto to AllocateResponse, and
it contains list of rejected regular resource request, and list of
increase/decrease container request.
Since it is an API change, please expect that more time/discussion required to
settle it down. Set target version to 2.9.
> add a way to tell AM container increase/decrease request is invalid
> -------------------------------------------------------------------
>
> Key: YARN-4495
> URL: https://issues.apache.org/jira/browse/YARN-4495
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: sandflee
> Attachments: YARN-4495.01.patch
>
>
> now RM may pass InvalidResourceRequestException to AM or just ignore the
> change request, the former will cause AMRMClientAsync down. and the latter
> will leave AM waiting for the relay.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
