From yarn-issues-return-138281-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Wed Feb 21 01:25:14 2018 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 F34A2180654 for ; Wed, 21 Feb 2018 01:25:13 +0100 (CET) Received: (qmail 726 invoked by uid 500); 21 Feb 2018 00:25:08 -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 715 invoked by uid 99); 21 Feb 2018 00:25:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Feb 2018 00:25:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 75141180334 for ; Wed, 21 Feb 2018 00:25:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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 (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 90qzjYFS1vlA for ; Wed, 21 Feb 2018 00:25:06 +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 71D355F58B for ; Wed, 21 Feb 2018 00:25:05 +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 75E66E0327 for ; Wed, 21 Feb 2018 00:25:03 +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 34E4B22856 for ; Wed, 21 Feb 2018 00:25:00 +0000 (UTC) Date: Wed, 21 Feb 2018 00:25:00 +0000 (UTC) From: "Young Chen (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (YARN-7708) [GPG] Load based policy generator 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-7708?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16370= 783#comment-16370783 ]=20 Young Chen edited comment on YARN-7708 at 2/21/18 12:24 AM: ------------------------------------------------------------ The rationale for this policy is to lower load on sub clusters that are rec= eiving an abnormal amount of jobs or are unable to keep up for performance = reasons. To alleviate job failures/excessive delays, this policy attempts t= o redirect load away from highly loaded sub clusters by updating a Weighted= LocalityPolicyManager with modified weights. This patch introduces the LoadBasedGlobalPolicy. It's configurable in the f= ollowing ways: * MAX_EDIT: The maximum number of sub clusters weights this policy will ed= it. The top N clusters by pending load will have their policy weights scale= d down. * MIN_PENDING: The minimum number of pending applications before a sub clu= ster weight qualifies for editing. * MAX_PENDING: The maximum number of pending applications in the scalable = range. Sub clusters exceeding this will have their policy weights set to MI= N_WEIGHT * MIN_WEIGHT: The minimum weight possible for a highly loaded sub cluster. * SCALING: The scaling method that maps pending load to sub cluster policy= weight. Currently there are three scaling methods: quadratic, log, and lin= ear.=C2=A0 was (Author: youchen): The rationale for this policy is to lower load on sub clusters that are rec= eiving an abnormal amount of jobs or are unable to keep up for performance = reasons. To alleviate job failures/excessive delays, this policy attempts t= o redirect load away from highly loaded sub clusters by updating a Weighted= LocalityPolicyManager with modified weights. This patch introduces the LoadBasedGlobalPolicy. It's configurable in the f= ollowing ways: * MAX_EDIT: The maximum number of sub clusters this policy will throttle. = The top N clusters by pending load will have their policy weights scaled do= wn. * MIN_PENDING: The minimum number of pending applications before a sub clu= ster weight qualifies for editing. * MAX_PENDING: The maximum number of pending applications in the scalable = range. Sub clusters exceeding this will have their policy weights set to MI= N_WEIGHT * MIN_WEIGHT: The minimum weight possible for a highly loaded sub cluster. * SCALING: The scaling method that maps pending load to sub cluster policy= weight. Currently there are three scaling methods: quadratic, log, and lin= ear.=C2=A0 > [GPG] Load based policy generator > --------------------------------- > > Key: YARN-7708 > URL: https://issues.apache.org/jira/browse/YARN-7708 > Project: Hadoop YARN > Issue Type: Sub-task > Reporter: Carlo Curino > Assignee: Young Chen > Priority: Major > Attachments: YARN-7708-YARN-7402.01.cumulative.patch > > > This policy reads load from the "pendingQueueLength" metrics and provides= scaling into a set of weights that influence the AMRMProxy and Router beha= viors. -- 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