From yarn-issues-return-156638-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Tue Oct 30 12:57:02 2018 Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-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 75D2C18970 for ; Tue, 30 Oct 2018 12:57:02 +0000 (UTC) Received: (qmail 50434 invoked by uid 500); 30 Oct 2018 12:57:02 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 50386 invoked by uid 500); 30 Oct 2018 12:57:02 -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 50375 invoked by uid 99); 30 Oct 2018 12:57:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Oct 2018 12:57:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id C8AAC1A0C58 for ; Tue, 30 Oct 2018 12:57:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id X46nIpT1KaWm for ; Tue, 30 Oct 2018 12:57:01 +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 F03535F358 for ; Tue, 30 Oct 2018 12:57:00 +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 959FAE25AA for ; Tue, 30 Oct 2018 12:57: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 2381327764 for ; Tue, 30 Oct 2018 12:57:00 +0000 (UTC) Date: Tue, 30 Oct 2018 12:57:00 +0000 (UTC) From: "Shane Kumpf (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6729) NM percentage-physical-cpu-limit should be always 100 if DefaultLCEResourcesHandler is used MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-6729?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16668= 663#comment-16668663 ]=20 Shane Kumpf commented on YARN-6729: ----------------------------------- Thanks, [~tangzhankun]! I'm good with that approach. I'll commit this short= ly unless there are other comments. {quote}One thing in my mind is that once we put "yarn.nodemanager.resource.= cpu.enabled" into the document. Does it mean that these features are stable= ? Because you know, for the historical reason, that settings are marked "un= stable". {quote} Enabling=C2=A0CgroupsLCEResourcesHandler follows the same code path, so I d= on't have much concern. We can discuss the annotations and removal of the d= eprecated code as part of YARN-8924. > NM percentage-physical-cpu-limit should be always 100 if DefaultLCEResour= cesHandler is used > -------------------------------------------------------------------------= ------------------ > > Key: YARN-6729 > URL: https://issues.apache.org/jira/browse/YARN-6729 > Project: Hadoop YARN > Issue Type: Bug > Components: nodemanager > Reporter: Yufei Gu > Assignee: Zhankun Tang > Priority: Major > Attachments: YARN-6729-trunk.001.patch > > > NM percentage-physical-cpu-limit is not honored in DefaultLCEResourcesHan= dler, which may cause container cpu usage calculation issue. e.g. container= vcore usage is potentially more than 100% if percentage-physical-cpu-limit= is set to a value less than 100.=20 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org