Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 6FE5818EBE for ; Thu, 24 Mar 2016 13:20:26 +0000 (UTC) Received: (qmail 45975 invoked by uid 500); 24 Mar 2016 13:20:26 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 45899 invoked by uid 500); 24 Mar 2016 13:20:26 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 45870 invoked by uid 99); 24 Mar 2016 13:20:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Mar 2016 13:20:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 750592C1F5C for ; Thu, 24 Mar 2016 13:20:25 +0000 (UTC) Date: Thu, 24 Mar 2016 13:20:25 +0000 (UTC) From: "Laxman (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MAPREDUCE-6659) Mapreduce App master waits long to kill containers on lost nodes. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210196#comment-15210196 ] Laxman commented on MAPREDUCE-6659: ----------------------------------- Please note that this issue happens with lost nodes (i.e, Unreachable hosts). NM crash with a reachable host is exhibiting a totally a different expected retry behavior. There liveness configurations are coming into play (yarn.resourcemanager.container.liveness-monitor.interval-ms, yarn.nm.liveness-monitor.expiry-interval-ms, yarn.am.liveness-monitor.expiry-interval-ms) as expected. > Mapreduce App master waits long to kill containers on lost nodes. > ----------------------------------------------------------------- > > Key: MAPREDUCE-6659 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-6659 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mr-am > Affects Versions: 2.6.0 > Reporter: Laxman > > MR Application master waits for very long time to cleanup and relaunch the tasks on lost nodes. Wait time is actually 2.5 hours (ipc.client.connect.max.retries * ipc.client.connect.max.retries.on.timeouts * ipc.client.connect.timeout = 10 * 45 * 20 = 9000 seconds = 2.5 hours) > Some similar issue related in RM-AM rpc protocol is fixed in YARN-3809. > As fixed in YARN-3809, we may need to introduce new configurations to control this RPC retry behavior. > Also, I feel this total retry time should honor and capped maximum to global task time out (mapreduce.task.timeout = 600000 default) -- This message was sent by Atlassian JIRA (v6.3.4#6332)