Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
Was reviewing the user-facing aspects that we are releasing as part of 2.8.0.
Looking at the 'AM blacklisting feature', I see several things to be fixed before we release it in 2.8.0.
Attachments
Attachments
Issue Links
- is related to
-
YARN-4685 Disable AM blacklisting by default to mitigate situations that application get hanged
- Resolved
- relates to
-
YARN-4790 Per user blacklist node for user specific error for container launch failure.
- Open
-
YARN-5063 Fail to launch AM continuously on a lost NM
- Open
-
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
- Resolved
-
YARN-4576 Enhancement for tracking Blacklist in AM Launching
- Open
-
YARN-2005 Blacklisting support for scheduling AMs
- Resolved