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 924212009C5 for ; Mon, 16 May 2016 23:29:16 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9100B160131; Mon, 16 May 2016 21:29:16 +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 DB46C160A19 for ; Mon, 16 May 2016 23:29:15 +0200 (CEST) Received: (qmail 73408 invoked by uid 500); 16 May 2016 21:29:13 -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 73097 invoked by uid 99); 16 May 2016 21:29:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 May 2016 21:29:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 541362C1F69 for ; Mon, 16 May 2016 21:29:13 +0000 (UTC) Date: Mon, 16 May 2016 21:29:13 +0000 (UTC) From: "Daniel Templeton (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4308) ContainersAggregated CPU resource utilization reports negative usage in first few heartbeats MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 16 May 2016 21:29:16 -0000 [ https://issues.apache.org/jira/browse/YARN-4308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285353#comment-15285353 ] Daniel Templeton commented on YARN-4308: ---------------------------------------- If the admin has to enable debug and bounce the daemon, the situation that caused the issue may not survive the bounce. In that case, I don't think adding a metric will be enough of an improvement over javadocs and comments to be worth it. I'm fine with just making sure that anyone hunting reasons for missing reports will trip over a pointer to the likely cause. > ContainersAggregated CPU resource utilization reports negative usage in first few heartbeats > -------------------------------------------------------------------------------------------- > > Key: YARN-4308 > URL: https://issues.apache.org/jira/browse/YARN-4308 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager > Affects Versions: 2.7.1 > Reporter: Sunil G > Assignee: Sunil G > Attachments: 0001-YARN-4308.patch, 0002-YARN-4308.patch > > > NodeManager reports ContainerAggregated CPU resource utilization as -ve value in first few heartbeats cycles. I added a new debug print and received below values from heartbeats. > {noformat} > INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl: ContainersResource Utilization : CpuTrackerUsagePercent : -1.0 > INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl:ContainersResource Utilization : CpuTrackerUsagePercent : 198.94598 > {noformat} > Its better we send 0 as CPU usage rather than sending a negative values in heartbeats eventhough its happening in only first few heartbeats. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org