Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
2.7.1
-
None
-
None
Description
This happens when the cluster is maxed out. One node is going bad, so everything that happens on it fails, so the bad node is never busy. Since the cluster is maxed out, when the RM looks for a node with available resources, it will always find the almost bad one because nothing can run on it so it has available resources.
Attachments
Issue Links
- duplicates
-
YARN-2005 Blacklisting support for scheduling AMs
- Resolved