From yarn-issues-return-137548-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Thu Feb 8 08:35:09 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 2BEB118064F for ; Thu, 8 Feb 2018 08:35:09 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1BD24160C4A; Thu, 8 Feb 2018 07:35:09 +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 6163E160C3D for ; Thu, 8 Feb 2018 08:35:08 +0100 (CET) Received: (qmail 49519 invoked by uid 500); 8 Feb 2018 07:35:07 -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 49508 invoked by uid 99); 8 Feb 2018 07:35:07 -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; Thu, 08 Feb 2018 07:35:07 +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 D2FD6C02AF for ; Thu, 8 Feb 2018 07:35:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 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, T_RP_MATCHES_RCVD=-0.01, 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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id sFSB13Atum9Z for ; Thu, 8 Feb 2018 07:35:06 +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 C5BC660DAE for ; Thu, 8 Feb 2018 07:35:03 +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 BC2D9E0424 for ; Thu, 8 Feb 2018 07:35:02 +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 208F624776 for ; Thu, 8 Feb 2018 07:35:01 +0000 (UTC) Date: Thu, 8 Feb 2018 07:35:01 +0000 (UTC) From: "stefanlee (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3933) FairScheduler: Multiple calls to completedContainer are not safe 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-3933?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16356= 599#comment-16356599 ]=20 stefanlee commented on YARN-3933: --------------------------------- [~yufeigu] thanks, yesterday, i found in our cluster the utilization rate o= f resource=C2=A0 is very low , but there is a lot of pending applications i= n it, and RM has no exception, then=C2=A0 i found a queue has negative-usag= e and also has pending resource, so i doubt=C2=A0Whether a queue has=C2=A0n= egative-usage resource can lead to FairScheduler do not assign containers t= o any other queues. thanks for this jira[https://issues.apache.org/jira/bro= wse/YARN-3933],=C2=A0it seems as same as my=C2=A0scenario. > FairScheduler: Multiple calls to completedContainer are not safe > ---------------------------------------------------------------- > > Key: YARN-3933 > URL: https://issues.apache.org/jira/browse/YARN-3933 > Project: Hadoop YARN > Issue Type: Bug > Components: fairscheduler > Affects Versions: 2.7.1 > Reporter: Lavkesh Lahngir > Assignee: Shiwei Guo > Priority: Major > Labels: oct16-medium > Fix For: 2.8.0, 3.0.0-alpha4 > > Attachments: YARN-3933.001.patch, YARN-3933.002.patch, YARN-3933.= 003.patch, YARN-3933.004.patch, YARN-3933.005.patch, YARN-3933.006.patch, y= arn-3933-branch-2.8.patch > > > In our cluster we are seeing available memory and cores being negative.= =20 > Initial inspection: > Scenario no. 1:=20 > In capacity scheduler the method allocateContainersToNode() checks if=20 > there are excess reservation of containers for an application, and they a= re no longer needed then it calls queue.completedContainer() which causes r= esources being negative. And they were never assigned in the first place.= =20 > I am still looking through the code. Can somebody suggest how to simulate= excess containers assignments ? -- 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