[
https://issues.apache.org/jira/browse/YARN-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunil G updated YARN-4389:
--------------------------
Attachment: 0006-YARN-4389.patch
Thank you [~rohithsharma]
Updating patch addressing the comments.
bq.do you think if app-level blacklistDisableThreshold is not configured,
should we consider global blacklistDisableThreshold?
Since this information is coming from AM end, and {{blacklistDisableThreshold}}
is a primitive type, I think it will have a value. Or we may need to see
whether its 0 and then try to get from global blackListThreshold. But there is
a chance that this can also be not configured, so we may need to fall to the
default of 0.8. Thoughts?
> "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
>
>
> "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)
