Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
We propose to add a queue in each NM, where queueable container requests can be held.
Based on the available resources in the node and the containers in the queue, the NM will decide when to allow the execution of a queued container.
In order to ensure the instantaneous start of a guaranteed-start container, the NM may decide to pre-empt/kill running queueable containers.
Attachments
Attachments
Issue Links
- is blocked by
-
YARN-4895 Add subtractFrom method to ResourceUtilization class
- Resolved
- is required by
-
YARN-5220 Scheduling of OPPORTUNISTIC containers through YARN RM
- Resolved
- relates to
-
YARN-4412 Create ClusterMonitor to compute ordered list of preferred NMs for OPPORTUNITIC containers
- Resolved
-
YARN-4738 Notify the RM about the status of OPPORTUNISTIC containers
- Resolved
-
YARN-5117 QueuingContainerManager does not start GUARANTEED Container even if Resources are available
- Resolved
-
YARN-5216 Expose configurable preemption policy for OPPORTUNISTIC containers running on the NM
- Resolved
-
YARN-5377 Fix TestQueuingContainerManager.testKillMultipleOpportunisticContainers
- Resolved
-
YARN-5541 Handling of opportunistic containers in the NM
- Open
-
YARN-4861 Define ContainerExitStatus for OPPORTUNISTIC containers that get killed
- Open