Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
This JIRA introduces the notion of container types.
We propose two initial types of containers: guaranteed-start and queueable containers.
Guaranteed-start are the existing containers, which are allocated by the central RM and are instantaneously started, once allocated.
Queueable is a new type of container, which allows containers to be queued in the NM, thus their execution may be arbitrarily delayed.
Attachments
Attachments
Issue Links
- blocks
-
YARN-2885 Create AMRMProxy request interceptor for distributed scheduling decisions for queueable containers
-
- Resolved
-
-
YARN-2877 Extend YARN to support distributed scheduling
-
- Resolved
-
-
YARN-1014 Configure OOM Killer to kill OPPORTUNISTIC containers first
-
- Resolved
-
- breaks
-
SLIDER-1130 Hadoop 2.8 YARN changes have broken slider
-
- Resolved
-
-
YARN-5184 Fix up incompatible changes introduced on ContainerStatus and NodeReport
-
- Resolved
-
- is depended upon by
-
YARN-1013 CS should watch resource utilization of containers and allocate speculative containers if appropriate
-
- Open
-
- is required by
-
YARN-4335 Allow ResourceRequests to specify ExecutionType of a request ask
-
- Resolved
-
-
YARN-5220 Scheduling of OPPORTUNISTIC containers through YARN RM
-
- Resolved
-
- relates to
-
YARN-3116 [Collector wireup] We need an assured way to determine if a container is an AM container on NM
-
- Resolved
-
-
YARN-5171 Extend DistributedSchedulerProtocol to notify RM of containers allocated by the Node
-
- Resolved
-
-
YARN-5541 Handling of opportunistic containers in the NM
-
- Open
-
-
YARN-10768 Preserve Opportunistic Containers when "findLostContainer"
-
- Open
-
-
YARN-5130 Mark ContainerStatus and NodeReport as evolving
-
- Patch Available
-