Details
-
Sub-task
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
3.0.0-beta1, 3.1.0
-
None
-
Reviewed
Description
When I submit an MR job that asks for too much memory or CPU for the map or reduce, the AM will fail because it recognizes that the request is too large. With any other resources, however, the resource requests will instead be made and remain pending forever. Looks like we forgot to update the code that tracks the maximum container allocation in ClusterNodeTracker.
Attachments
Attachments
Issue Links
- breaks
-
YARN-7589 TestPBImplRecords fails with NullPointerException
- Resolved