[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 - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Critical
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 2.8.0, 3.0.0-alpha1
Component/s: applications
Labels:
None

Target Version/s:

2.8.0
Hadoop Flags:

Reviewed

Description

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

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

0001-YARN-4389.patch
25/Nov/15 12:05
20 kB
Sunil G
0002-YARN-4389.patch
02/Dec/15 17:00
21 kB
Sunil G
0003-YARN-4389.patch
09/Dec/15 17:21
20 kB
Sunil G
0004-YARN-4389.patch
18/Dec/15 14:44
20 kB
Sunil G
0005-YARN-4389.patch
06/Jan/16 17:34
20 kB
Sunil G
0006-YARN-4389.patch
13/Jan/16 11:51
21 kB
Sunil G
0007-YARN-4389.patch
13/Jan/16 16:07
21 kB
Sunil G
0008-YARN-4389.patch
14/Jan/16 15:23
21 kB
Sunil G
0009-YARN-4389.patch
14/Jan/16 17:20
24 kB
Sunil G
0009-YARN-4389-branch-2.patch
15/Jan/16 17:06
24 kB
Sunil G

Issue Links

is related to

YARN-4837 User facing aspects of 'AM blacklisting' feature need fixing

Resolved

YARN-4576 Enhancement for tracking Blacklist in AM Launching

Open

Activity

People

Assignee:: Sunil G

Reporter:: Junping Du

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Dates

Created:: 24/Nov/15 17:08

Updated:: 25/Oct/19 20:27

Resolved:: 15/Jan/16 17:23