Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
Currently, the NM immediately launches containers after resource localization. Several features could be more cleanly implemented if the NM included a separate stage for reserving resources.
Attachments
Attachments
Issue Links
- breaks
-
YARN-7248 NM returns new SCHEDULED container status to older clients
- Resolved
- causes
-
YARN-8331 Race condition in NM container launched after done
- Resolved
- is related to
-
MAPREDUCE-7205 Treat container scheduler kill exit code as a task attempt killing event
- Resolved
- is required by
-
YARN-4972 Cleanup ContainerScheduler tests to remove long sleep times
- Open
-
YARN-5541 Handling of opportunistic containers in the NM
- Open
- relates to
-
YARN-2877 Extend YARN to support distributed scheduling
- Resolved
- links to