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 6562F18BA5 for ; Fri, 15 Jan 2016 15:10:40 +0000 (UTC) Received: (qmail 79368 invoked by uid 500); 15 Jan 2016 15:10:40 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 79266 invoked by uid 500); 15 Jan 2016 15:10:40 -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 79234 invoked by uid 99); 15 Jan 2016 15:10:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jan 2016 15:10:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id DB7922C1F64 for ; Fri, 15 Jan 2016 15:10:39 +0000 (UTC) Date: Fri, 15 Jan 2016 15:10:39 +0000 (UTC) From: "Junping Du (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4389) "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster 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-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101889#comment-15101889 ] Junping Du commented on YARN-4389: ---------------------------------- Hi [~rohithsharma], this is on my mind too when I raise my previous comments. However, in YARN-4576, we are talking about have a real global blacklist tracking rather than per app list. May be we can put a note there and track this later? > "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be app specific rather than a setting for whole YARN cluster > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: YARN-4389 > URL: https://issues.apache.org/jira/browse/YARN-4389 > Project: Hadoop YARN > Issue Type: Bug > Components: applications > Reporter: Junping Du > Assignee: Sunil G > Priority: Critical > Attachments: 0001-YARN-4389.patch, 0002-YARN-4389.patch, 0003-YARN-4389.patch, 0004-YARN-4389.patch, 0005-YARN-4389.patch, 0006-YARN-4389.patch, 0007-YARN-4389.patch, 0008-YARN-4389.patch, 0009-YARN-4389.patch > > > "yarn.am.blacklisting.enabled" and "yarn.am.blacklisting.disable-failure-threshold" should be application specific rather than a setting in cluster level, or we should't maintain amBlacklistingEnabled and blacklistDisableThreshold in per rmApp level. We should allow each am to override this config, i.e. via submissionContext. -- This message was sent by Atlassian JIRA (v6.3.4#6332)