From yarn-issues-return-163863-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Sat Feb 23 17:42:06 2019 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 CD830199BE for ; Sat, 23 Feb 2019 17:42:06 +0000 (UTC) Received: (qmail 74083 invoked by uid 500); 23 Feb 2019 17:42:06 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 74030 invoked by uid 500); 23 Feb 2019 17:42:06 -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 74019 invoked by uid 99); 23 Feb 2019 17:42:06 -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; Sat, 23 Feb 2019 17:42:06 +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 17CD5C22F2 for ; Sat, 23 Feb 2019 17:42:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 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, 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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id Nz1NfK7dl8Jb for ; Sat, 23 Feb 2019 17:42:04 +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 ED3A962456 for ; Sat, 23 Feb 2019 17:42:02 +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 A7544E27E5 for ; Sat, 23 Feb 2019 17:42: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 8DFD524558 for ; Sat, 23 Feb 2019 17:42:00 +0000 (UTC) Date: Sat, 23 Feb 2019 17:42:00 +0000 (UTC) From: =?utf-8?Q?=C3=8D=C3=B1igo_Goiri_=28JIRA=29?= To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-999) In case of long running tasks, reduce node resource should balloon out resource quickly by calling preemption API and suspending running task. 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-999?page=3Dcom.atlassian.j= ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D167759= 57#comment-16775957 ]=20 =C3=8D=C3=B1igo Goiri commented on YARN-999: ---------------------------------- [^YARN-999.005.patch] includes full coverage in the tests. Summarizing, the functionality is: * It just reduces the resources if we don't give a timeout. * Triggers preemption (notify AM) when we get the change of resources with = a timeout. * Triggers killing in the heartbeats when the timeout is passed. * It tries to preempt/kill OPPORTUNISTIC containers first, then GUARANTEED = and finally AMs (this is in creation time order). [~djp], can you take a look and see if there is anything else left? > In case of long running tasks, reduce node resource should balloon out re= source quickly by calling preemption API and suspending running task.=20 > -------------------------------------------------------------------------= ---------------------------------------------------------------------- > > Key: YARN-999 > URL: https://issues.apache.org/jira/browse/YARN-999 > Project: Hadoop YARN > Issue Type: Sub-task > Components: graceful, nodemanager, scheduler > Reporter: Junping Du > Assignee: =C3=8D=C3=B1igo Goiri > Priority: Major > Attachments: YARN-291.000.patch, YARN-999.001.patch, YARN-999.002= .patch, YARN-999.003.patch, YARN-999.004.patch, YARN-999.005.patch > > > In current design and implementation, when we decrease resource on node t= o less than resource consumption of current running tasks, tasks can still = be running until the end. But just no new task get assigned on this node (b= ecause AvailableResource < 0) until some tasks are finished and AvailableRe= source > 0 again. This is good for most cases but in case of long running t= ask, it could be too slow for resource setting to actually work so preempti= on could be used here. -- 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