Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 45E06200CEF for ; Mon, 21 Aug 2017 06:08:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 444AB163B90; Mon, 21 Aug 2017 04:08:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8B3DF163B8E for ; Mon, 21 Aug 2017 06:08:04 +0200 (CEST) Received: (qmail 82804 invoked by uid 500); 21 Aug 2017 04:08:03 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 82793 invoked by uid 99); 21 Aug 2017 04:08:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Aug 2017 04:08:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 11961C00E2 for ; Mon, 21 Aug 2017 04:08:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id fptyrlSP42En for ; Mon, 21 Aug 2017 04:08:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 9BF195FAE1 for ; Mon, 21 Aug 2017 04:08:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DC44CE0C21 for ; Mon, 21 Aug 2017 04:08:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4807925386 for ; Mon, 21 Aug 2017 04:08:00 +0000 (UTC) Date: Mon, 21 Aug 2017 04:08:00 +0000 (UTC) From: "kartheek muthyala (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6979) Add flag to notify all types of container updates to NM via NodeHeartbeatResponse MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 21 Aug 2017 04:08:05 -0000 [ https://issues.apache.org/jira/browse/YARN-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134685#comment-16134685 ] kartheek muthyala commented on YARN-6979: ----------------------------------------- Thank you Arun for the review and committing this to trunk. > 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 (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