hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6979) Add flag to allow all container updates to be initiated via NodeHeartbeatResponse
Date Sun, 20 Aug 2017 14:29:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134444#comment-16134444
] 

Arun Suresh commented on YARN-6979:
-----------------------------------

+1, Will check this in shortly

> 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, YARN-6979.002.patch, YARN-6979.003.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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message