Details
Description
YARN-4161 adds a configuration yarn.scheduler.capacity.per-node-heartbeat.maximum-container-assignments to control max number of container assignments per heartbeat, however the default value is -1. This could potentially cause the CS gets stuck in the while loop causing issue like YARN-8513. We should change this to a finite number, e.g 100.
Attachments
Attachments
Issue Links
- breaks
-
YARN-8944 TestContainerAllocation.testUserLimitAllocationMultipleContainers failure after YARN-8896
- Resolved
- causes
-
YARN-8513 CapacityScheduler infinite loop when queue is near fully utilized
- Resolved
- is duplicated by
-
YARN-10440 resource manager hangs,and i cannot submit any new jobs,but rm and nm processes are normal
- Reopened
- is related to
-
YARN-8513 CapacityScheduler infinite loop when queue is near fully utilized
- Resolved
- relates to
-
YARN-8915 Update the doc about the default value of "maximum-container-assignments" for capacity scheduler
- Resolved