[
https://issues.apache.org/jira/browse/YARN-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandflee updated YARN-4495:
---------------------------
Attachment: YARN-4495.01.patch
just protocol change, add FailedResourceChange to AllocateResponse, represents
which container why container change request is failed.
{code}
public static FailedResourceChange newInstance(
ContainerId containerId,
ResourceChangeFailStatus failStatus, String failMsg) {
FailedResourceChange context = Records
.newRecord(FailedResourceChange.class);
context.setContainerId(containerId);
context.setFailStatus(failStatus);
context.setFailMsg(failMsg);
return context;
}
{code}
> 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)
