hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6979) Add flag to notify all types of container updates to NM via NodeHeartbeatResponse
Date Mon, 21 Aug 2017 18:25:00 GMT

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

Wangda Tan commented on YARN-6979:

[~asuresh], is there any compatibility issue of the patch? I saw some protocols are added
since 2.8.0. See YARN-1644. 

> Add flag to notify all types of container updates to NM 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
>             Fix For: 2.9.0, 3.0.0-beta1
>         Attachments: YARN-6979.001.patch, YARN-6979.002.patch, YARN-6979.003.patch, YARN-6979.addendum-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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message