-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.8.0
-
Fix Version/s: 2.9.0, 3.0.0-alpha1
-
Component/s: fairscheduler
-
Labels:None
-
Target Version/s:
-
Hadoop Flags:Reviewed
The maxAMShare uses the queue's policy for enforcing limits. When using FAIR policy, this considers only memory. If there are fewer vcores on the cluster, the AMs can end up taking all the vcores leading to a livelock.
- duplicates
-
YARN-3621 FairScheduler doesn't count AM vcores towards max-share
-
- Resolved
-