From yarn-issues-return-162483-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Sun Feb 3 06:59:04 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 72C69180674 for ; Sun, 3 Feb 2019 07:59:04 +0100 (CET) Received: (qmail 55494 invoked by uid 500); 3 Feb 2019 06:59:03 -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 55483 invoked by uid 99); 3 Feb 2019 06:59:03 -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; Sun, 03 Feb 2019 06:59:03 +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 F2708C26E2 for ; Sun, 3 Feb 2019 06:59:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, 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-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 Eibg55p9qUzP for ; Sun, 3 Feb 2019 06:59:01 +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 7D09361114 for ; Sun, 3 Feb 2019 06:59: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 BABEDE26BC for ; Sun, 3 Feb 2019 06:59: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 20146243EE for ; Sun, 3 Feb 2019 06:59:00 +0000 (UTC) Date: Sun, 3 Feb 2019 06:59:00 +0000 (UTC) From: "Zhaohui Xin (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-9276) Filter non-existent resource requests actively 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-9276?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:all-tabpanel ] Zhaohui Xin updated YARN-9276: ------------------------------ Description:=20 In some scenarios, applications will request nonexistent resource name in t= his cluster, such as nonexistent hosts or racks. Obviously, we should filter or degrade these invaild resource requests acti= vely. *This is especially effective when HDFS and Yarn are deployed on different = nodes, and the scheduling throughput of one of our clusters has improved by= {color:#FF0000}5X{color}.* =C2=A0 =C2=A0 was: In some scenarios, applications will request nonexistent resource name in t= his cluster, such as nonexistent hosts or racks. Obviously, we should filter or degrade these invaild resource requests acti= vely. This is especially effective when HDFS and Yarn are deployed on different n= odes, and the scheduling throughput of one of our clusters has improved by = 5X. > Filter non-existent resource requests actively > ---------------------------------------------- > > Key: YARN-9276 > URL: https://issues.apache.org/jira/browse/YARN-9276 > Project: Hadoop YARN > Issue Type: Bug > Components: RM, scheduler > Affects Versions: 2.6.0, 2.7.0, 2.8.0, 2.9.0, 3.0.0, 3.1.0 > Reporter: Zhaohui Xin > Assignee: Zhaohui Xin > Priority: Major > Attachments: image-2019-02-03-14-58-31-246.png, image-2019-02-03-= 14-58-48-148.png > > > In some scenarios, applications will request nonexistent resource name in= this cluster, such as nonexistent hosts or racks. > Obviously, we should filter or degrade these invaild resource requests ac= tively. > *This is especially effective when HDFS and Yarn are deployed on differen= t nodes, and the scheduling throughput of one of our clusters has improved = by {color:#FF0000}5X{color}.* > =C2=A0 > =C2=A0 -- 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