Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 21BFF18C04 for ; Thu, 17 Dec 2015 21:04:47 +0000 (UTC) Received: (qmail 41337 invoked by uid 500); 17 Dec 2015 21:04:46 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 41293 invoked by uid 500); 17 Dec 2015 21:04:46 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 41280 invoked by uid 99); 17 Dec 2015 21:04:46 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Dec 2015 21:04:46 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id A9C492C1F73 for ; Thu, 17 Dec 2015 21:04:46 +0000 (UTC) Date: Thu, 17 Dec 2015 21:04:46 +0000 (UTC) From: "Wangda Tan (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-12356) CPU usage statistics on Windows MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-12356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062809#comment-15062809 ] Wangda Tan commented on HADOOP-12356: ------------------------------------- Hi [~elgoiri]/[~cnauroth], Looked at patch and discussions: bq. Inigo Goiri, my understanding of the resource monitoring code at this layer is that it needs to track utilization as a percentage, not in units of vcores. I'd also be concerned that changing this calculation could cause unusual effects during a rolling upgrade scenario, when some NodeManagers are running the old calculation and some NodeManagers are running the new calculation. I expect Wangda can give us a more definitive answer. Since the ResourceUtilization is in 2.8.0 only, I think the rolling upgrade is not an issue. I'm wondering if we have different behaviors in SysInfoLinux and SysInfoWindows to get CPU usage: - Linux normalized to 0-100%: a node with 8 cores, and usages are all 50%, the returned accumulated usage after normalization is 50%. - Windows is not normalized to 0-100%: a node with 8 cores, and usages are all 50%, the returned accumulated usage is 400%. I think we should make sure the two SysInfo implementation has consistency behavior, maybe we need add the behavior description to SysInfo#getCPUUsage java docs. I'm fine with the change of NodeResourceMonitorImpl if SysInfoWindows/Linux both normalized usage to 0-100%. > CPU usage statistics on Windows > ------------------------------- > > Key: HADOOP-12356 > URL: https://issues.apache.org/jira/browse/HADOOP-12356 > Project: Hadoop Common > Issue Type: Bug > Components: util > Environment: CPU: Intel Xeon > OS: Windows server > Reporter: Yunqi Zhang > Assignee: Yunqi Zhang > Labels: easyfix, newbie, patch > Attachments: 0001-Correct-the-CPU-usage-calcualtion.patch, 0001-Correct-the-CPU-usage-calcualtion.patch, HADOOP-12356-v3.patch > > Original Estimate: 2h > Remaining Estimate: 2h > > The CPU usage information on Windows is computed incorrectly. The proposed patch fixes the issue, and unifies the the interface with Linux. -- This message was sent by Atlassian JIRA (v6.3.4#6332)