Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
In the current implementation, opportunistic containers are allocated based on the number of queued opportunistic container information received in node heartbeat. This information becomes stale as soon as more opportunistic containers are allocated on that node.
Allocation of opportunistic containers happens on the same heartbeat in which AM asks for the containers. When multiple applications request for Opportunistic containers, containers might get allocated on the same set of nodes as already allocated containers on the node are not considered while serving requests from different applications. This can lead to uneven allocation of Opportunistic containers across the cluster leading to increased queuing time
Attachments
Attachments
Issue Links
- breaks
-
YARN-10040 DistributedShell test failure on X86 and ARM
- Resolved
- depends upon
-
YARN-9859 Refactor OpportunisticContainerAllocator
- Resolved