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 F0ED910E85 for ; Tue, 22 Oct 2013 18:44:59 +0000 (UTC) Received: (qmail 615 invoked by uid 500); 22 Oct 2013 18:43:07 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 438 invoked by uid 500); 22 Oct 2013 18:42:55 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 403 invoked by uid 99); 22 Oct 2013 18:42:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Oct 2013 18:42:51 +0000 Date: Tue, 22 Oct 2013 18:42:51 +0000 (UTC) From: "Karthik Kambatla (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1183) MiniYARNCluster shutdown takes several minutes intermittently 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/YARN-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802109#comment-13802109 ] Karthik Kambatla commented on YARN-1183: ---------------------------------------- In the past, we have run into cases where the default concurrency level led to high memory usage. MAPREDUCE-5368 is one example. While I do agree that it might not lead to big differences for something "short-lived" like MiniYARNCluster, I think it is good practice to use a smaller value when we know the number of concurrent accesses is low. > MiniYARNCluster shutdown takes several minutes intermittently > ------------------------------------------------------------- > > Key: YARN-1183 > URL: https://issues.apache.org/jira/browse/YARN-1183 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Andrey Klochkov > Assignee: Andrey Klochkov > Attachments: YARN-1183--n2.patch, YARN-1183--n3.patch, YARN-1183--n4.patch, YARN-1183.patch > > > As described in MAPREDUCE-5501 sometimes M/R tests leave MRAppMaster java processes living for several minutes after successful completion of the corresponding test. There is a concurrency issue in MiniYARNCluster shutdown logic which leads to this. Sometimes RM stops before an app master sends it's last report, and then the app master keeps retrying for >6 minutes. In some cases it leads to failures in subsequent tests, and it affects performance of tests as app masters eat resources. -- This message was sent by Atlassian JIRA (v6.1#6144)