Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
Currently, id, resource request etc need to be copied over from Container to ContainerLaunchContext. This can be brittle. Also it leads to duplication of information (such as Resource from CLC and Resource from Container and Container.tokens). Sending Container directly to startContainer solves these problems. It also makes CLC clean by only having stuff in it that it set by the client/AM.
Attachments
Attachments
Issue Links
- is related to
-
YARN-382 SchedulerUtils improve way normalizeRequest sets the resource capabilities
- Closed
- relates to
-
MAPREDUCE-5139 Update MR App after YARN-486
- Closed
-
MAPREDUCE-5152 MR App is not using Container from RM
- Closed