[
https://issues.apache.org/jira/browse/YARN-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Suresh updated YARN-6979:
------------------------------
Description:
Currently, only the Container Resource decrease command is sent to the NM via
NodeHeartbeat response. This JIRA proposes to add a flag in the RM to allow ALL
container updates (increase, decrease, promote and demote) to be initiated via
node HB.
The AM is still free to use the ContainerManagementPrototol's
{{updateContainer}} API in cases where for instance, the Node HB frequency is
very low and the AM needs to update the container as soon as possible. In these
situations, if the Node HB arrives before the updateContainer API call, the
call would error out, due to a version mismatch and the AM is required to
handle it.
was:
Currently, only the Container Resource decrease command is sent to the NM via
NodeHeartbeat response. This JIRA proposes to add a flag in the RM to allow ALL
container updates (increase, decrease, promote and demote) to initiated via
node HB.
The AM is still free to use the ContainerManagementPrototol's
{{updateContainer}} API in cases where for instance, the Node HB frequency is
very low and the AM needs to update the container as soon as possible. In these
situations, if the Node HB arrives before the updateContainer API call, the
call would error out, due to a version mismatch and the AM is required to
handle it.
> Add flag to allow all container updates to be initiated via
> NodeHeartbeatResponse
> ---------------------------------------------------------------------------------
>
> Key: YARN-6979
> URL: https://issues.apache.org/jira/browse/YARN-6979
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: kartheek muthyala
> Attachments: YARN-6979.001.patch
>
>
> Currently, only the Container Resource decrease command is sent to the NM via
> NodeHeartbeat response. This JIRA proposes to add a flag in the RM to allow
> ALL container updates (increase, decrease, promote and demote) to be
> initiated via node HB.
> The AM is still free to use the ContainerManagementPrototol's
> {{updateContainer}} API in cases where for instance, the Node HB frequency is
> very low and the AM needs to update the container as soon as possible. In
> these situations, if the Node HB arrives before the updateContainer API call,
> the call would error out, due to a version mismatch and the AM is required to
> handle it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
