[YARN-486] Change startContainer NM API to accept Container as a parameter and make ContainerLaunchContext user land - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Sub-task
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 2.1.0-beta
Component/s: None
Labels:
None

Hadoop Flags:

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

- Sort By Name
- Sort By Date
- Ascending
- Descending

YARN-486.1.patch
08/Apr/13 18:09
117 kB
Xuan Gong
YARN-486.2.patch
08/Apr/13 20:02
117 kB
Xuan Gong
YARN-486.3.patch
08/Apr/13 23:01
121 kB
Xuan Gong
YARN-486.4.patch
09/Apr/13 00:18
115 kB
Xuan Gong
YARN-486.5.patch
10/Apr/13 22:15
131 kB
Xuan Gong
YARN-486.6.patch
11/Apr/13 00:25
135 kB
Xuan Gong
YARN-486-20130410.txt
11/Apr/13 02:33
136 kB
Vinod Kumar Vavilapalli
YARN-486.6.branch2.patch
11/Apr/13 22:50
136 kB
Xuan Gong

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

Activity

People

Assignee:: Xuan Gong

Reporter:: Bikas Saha

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Dates

Created:: 18/Mar/13 22:43

Updated:: 27/Aug/13 22:15

Resolved:: 11/Apr/13 23:05