From yarn-issues-return-135831-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Wed Jan 24 11:54:04 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 A99BE180630 for ; Wed, 24 Jan 2018 11:54:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 99546160C3C; Wed, 24 Jan 2018 10:54:04 +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 DEC91160C2E for ; Wed, 24 Jan 2018 11:54:03 +0100 (CET) Received: (qmail 13649 invoked by uid 500); 24 Jan 2018 10:54: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 13638 invoked by uid 99); 24 Jan 2018 10:54:02 -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; Wed, 24 Jan 2018 10:54:02 +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 6B9F8C3DC2 for ; Wed, 24 Jan 2018 10:54:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -107.911 X-Spam-Level: X-Spam-Status: No, score=-107.911 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, 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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id UCuzHXo5i56z for ; Wed, 24 Jan 2018 10:54: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 1BC475F24B for ; Wed, 24 Jan 2018 10:54: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 59029E0F37 for ; Wed, 24 Jan 2018 10:54: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 14619240EE for ; Wed, 24 Jan 2018 10:54:00 +0000 (UTC) Date: Wed, 24 Jan 2018 10:54:00 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-7790) Improve Capacity Scheduler Async Scheduling to better handle node failures 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-7790?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16337= 384#comment-16337384 ]=20 Wangda Tan commented on YARN-7790: ---------------------------------- Thanks [~sunilg] for reviewing the patch, addressed comments and uploaded v= er.3 patch. > Improve Capacity Scheduler Async Scheduling to better handle node failure= s > -------------------------------------------------------------------------= - > > Key: YARN-7790 > URL: https://issues.apache.org/jira/browse/YARN-7790 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Sumana Sathish > Assignee: Wangda Tan > Priority: Critical > Attachments: YARN-7790.001.patch, YARN-7790.002.patch > > > This is not a new issue but async scheduling makes it worse: > In sync scheduling, if an AM container allocated to a node, it assumes no= de just heartbeat to RM, and AM launcher will connect NM to=C2=A0launch the= container. Even though it is possible that NM crashes after the heartbeat,= which causes AM hangs for a while. But it is related rare. > In async scheduling world, multiple AM containers can be placed on a prob= lematic NM, which could cause application hangs easily. Discussed with [~su= nilg] and [~jianhe] , we need one fix: > When async scheduling enabled: > - Skip node which missed X node heartbeat. > And in addition, it's better to reduce wait time by setting following con= figs to earlier fail a container being launched=C2=A0at an NM with connecti= vity issue. > {code:java} > RetryPolicy retryPolicy =3D > createRetryPolicy(conf, > YarnConfiguration.CLIENT_NM_CONNECT_MAX_WAIT_MS, > YarnConfiguration.DEFAULT_CLIENT_NM_CONNECT_MAX_WAIT_MS, > YarnConfiguration.CLIENT_NM_CONNECT_RETRY_INTERVAL_MS, > YarnConfiguration.DEFAULT_CLIENT_NM_CONNECT_RETRY_INTERVAL_MS); > {code} > The second part is not covered by the patch. -- 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