Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 16 Aug 2017 05:23:00 +0000 (UTC)
From: "Arun Suresh (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13093623.1502318945000.40367.1502860980714@Atlassian.JIRA>
In-Reply-To: <JIRA.13093623.1502318945000@Atlassian.JIRA>
References: <JIRA.13093623.1502318945000@Atlassian.JIRA> <JIRA.13093623.1502318945782@jira-lw-us.apache.org>
Subject: [jira] [Updated] (YARN-6979) Add flag to allow all container
 updates to be initiated via NodeHeartbeatResponse
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 16 Aug 2017 05:23:05 -0000


     [ 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 increase 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.

  was:
Currently, only the Container Resource increase 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 is 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
>
> Currently, only the Container Resource increase 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.


--
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