hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohith Sharma K S (JIRA)" <j...@apache.org>
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
Date Fri, 15 Jan 2016 16:22:39 GMT

    [ https://issues.apache.org/jira/browse/YARN-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102002#comment-15102002

Rohith Sharma K S commented on YARN-4389:

[~sunilg] I committed to trunk. Cheery-pick for branch-2 is failing. Could you provide patch
for branch-2 and branch-2.8 please

> "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,
> "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

View raw message