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 EA0FB200D5C for ; Fri, 15 Dec 2017 11:36:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E86FE160C14; Fri, 15 Dec 2017 10:36: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 3A78A160C06 for ; Fri, 15 Dec 2017 11:36:05 +0100 (CET) Received: (qmail 26549 invoked by uid 500); 15 Dec 2017 10:36:04 -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 26538 invoked by uid 99); 15 Dec 2017 10:36:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Dec 2017 10:36:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E8313C700D for ; Fri, 15 Dec 2017 10:36:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.211 X-Spam-Level: X-Spam-Status: No, score=-99.211 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id QnLiq0dR7Dta for ; Fri, 15 Dec 2017 10:36:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 13F5E5FB70 for ; Fri, 15 Dec 2017 10:36:02 +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 8F9D0E256E for ; Fri, 15 Dec 2017 10:36:01 +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 BAB532740D for ; Fri, 15 Dec 2017 10:36:00 +0000 (UTC) Date: Fri, 15 Dec 2017 10:36:00 +0000 (UTC) From: "Yang Wang (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-7660) NM node resource should be updated through heartbeat when rmadmin updateNodeResource execute successfully MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 15 Dec 2017 10:36:06 -0000 [ https://issues.apache.org/jira/browse/YARN-7660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Wang updated YARN-7660: ---------------------------- Description: When yarn rmadmin -updateNodeResource is used to update node resource, and execute successfully. The new capability should be sent to NM througn RM-NM heartbeat. 1. NM jmx metrics need to be updated 2. NM cgroup quota need to be updated was: {code:title=NodeManagerMetrics.java} public void addResource(Resource res) { availableMB = availableMB + res.getMemorySize(); availableGB.incr((int)Math.floor(availableMB/1024d)); availableVCores.incr(res.getVirtualCores()); } {code} When the node resource was updated through RM-NM heartbeat, the NM metric will get wrong value. The root cause of this issue is that new resource has been added to availableMB, so not needed to increase for availableGB again. > NM node resource should be updated through heartbeat when rmadmin updateNodeResource execute successfully > --------------------------------------------------------------------------------------------------------- > > Key: YARN-7660 > URL: https://issues.apache.org/jira/browse/YARN-7660 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Yang Wang > > When yarn rmadmin -updateNodeResource is used to update node resource, and execute successfully. The new capability should be sent to NM througn RM-NM heartbeat. > 1. NM jmx metrics need to be updated > 2. NM cgroup quota need to be updated -- 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