From yarn-issues-return-136805-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Wed Jan 31 18:32:05 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 D5F88180662 for ; Wed, 31 Jan 2018 18:32:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C499A160C42; Wed, 31 Jan 2018 17:32: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 17882160C2C for ; Wed, 31 Jan 2018 18:32:04 +0100 (CET) Received: (qmail 57616 invoked by uid 500); 31 Jan 2018 17:32: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 57604 invoked by uid 99); 31 Jan 2018 17:32:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Jan 2018 17:32:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 95115C051D for ; Wed, 31 Jan 2018 17:32:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id YEFcoyHngZoK for ; Wed, 31 Jan 2018 17:32:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id A80A660E0E for ; Wed, 31 Jan 2018 17:32:01 +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 D7D11E0220 for ; Wed, 31 Jan 2018 17:32: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 53BF124116 for ; Wed, 31 Jan 2018 17:32:00 +0000 (UTC) Date: Wed, 31 Jan 2018 17:32:00 +0000 (UTC) From: "Manikandan R (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (YARN-4606) CapacityScheduler: applications could get starved because computation of #activeUsers considers pending apps 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-4606?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16347= 236#comment-16347236 ]=20 Manikandan R edited comment on YARN-4606 at 1/31/18 5:31 PM: ------------------------------------------------------------- Thanks [~eepayne] [~sunilg] for your comments.=C2=A0 {quote}And when we need to know all active users in cluster (for user-limit= computation etc) we might need to use=C2=A0activeUsers+activeUsersOfPendin= gApps.{quote} Shouldn't we use=C2=A0activeUsersOfPendingApps only for user limit calculat= ion? Otherwise, based on the example given in the description, Won't we end= up in same situation (2+2 =3D=3D 4 )? Please correct my understanding. =C2=A0 was (Author: manirajv06@gmail.com): Thanks [~eepayne] [~sunilg] for your comments. {quote}And when we need to know all active users in cluster (for user-limit= computation etc) we might need to use=C2=A0activeUsers+activeUsersOfPendin= gApps.\{quote} Shouldn't we use=C2=A0activeUsersOfPendingApps only for user limit calculat= ion? Otherwise, based on the example given in the description, Won't we end= up in same situation (2+2 =3D=3D 4 )? Please correct my understanding. =C2=A0 > CapacityScheduler: applications could get starved because computation of = #activeUsers considers pending apps=20 > -------------------------------------------------------------------------= ------------------------------------ > > Key: YARN-4606 > URL: https://issues.apache.org/jira/browse/YARN-4606 > Project: Hadoop YARN > Issue Type: Bug > Components: capacity scheduler, capacityscheduler > Affects Versions: 2.8.0, 2.7.1 > Reporter: Karam Singh > Assignee: Wangda Tan > Priority: Critical > Attachments: YARN-4606.1.poc.patch > > > Currently, if all applications belong to same user in LeafQueue are pendi= ng (caused by max-am-percent, etc.), ActiveUsersManager still considers the= user is an active user. This could lead to starvation of active applicatio= ns, for example: > - App1(belongs to user1)/app2(belongs to user2) are active, app3(belongs = to user3)/app4(belongs to user4) are pending > - ActiveUsersManager returns #active-users=3D4 > - However, there're only two users (user1/user2) are able to allocate new= resources. So computed user-limit-resource could be lower than expected. -- 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