From yarn-issues-return-137117-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Fri Feb 2 18:29:03 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 B49EE17930 for ; Fri, 2 Feb 2018 18:29:03 +0000 (UTC) Received: (qmail 93186 invoked by uid 500); 2 Feb 2018 18:29:03 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 93137 invoked by uid 500); 2 Feb 2018 18:29: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 93094 invoked by uid 99); 2 Feb 2018 18:29:03 -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; Fri, 02 Feb 2018 18:29:03 +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 02F08C0FED for ; Fri, 2 Feb 2018 18:29:02 +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 DTbROMzMre6Q for ; Fri, 2 Feb 2018 18:29:02 +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 DB5575F1BE for ; Fri, 2 Feb 2018 18:29: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 74840E00FC for ; Fri, 2 Feb 2018 18:29:01 +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 38FAD21E8C for ; Fri, 2 Feb 2018 18:29:00 +0000 (UTC) Date: Fri, 2 Feb 2018 18:29:00 +0000 (UTC) From: "Arun Suresh (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-7839) Modify PlacementAlgorithm to Check node capacity before placing request on node 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-7839?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:all-tabpanel ] Arun Suresh updated YARN-7839: ------------------------------ Summary: Modify PlacementAlgorithm to Check node capacity before placin= g request on node (was: Check node capacity before placing in the Algorith= m) > Modify PlacementAlgorithm to Check node capacity before placing request o= n node > -------------------------------------------------------------------------= ------ > > Key: YARN-7839 > URL: https://issues.apache.org/jira/browse/YARN-7839 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Arun Suresh > Assignee: Panagiotis Garefalakis > Priority: Major > Attachments: YARN-7839-YARN-6592.001.patch > > > Currently, the Algorithm assigns a node to a request=C2=A0purely based on= if the constraints are met. It is later in the scheduling phase that the Q= ueue capacity and Node capacity are checked. If the request cannot be place= d because of unavailable Queue/Node capacity, the request is retried by the= Algorithm. > For clusters that are running at high utilization, we can reduce the retr= ies if we perform the Node capacity check in the Algorithm as well. The Que= ue capacity check and the other user limit checks can still be handled by t= he scheduler (since queues and other limits are tied to the scheduler, and = not scheduler agnostic) -- 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