[YARN-5085] Add support for change of container ExecutionType - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 2.9.0, 3.0.0
Component/s: None
Labels:
None

Release Note:

Hide
This allows the Application Master to ask the Scheduler to change the ExecutionType of a running/allocated container.

Show
This allows the Application Master to ask the Scheduler to change the ExecutionType of a running/allocated container.

Description

~~YARN-2882~~ introduced the concept of ExecutionType for containers and it also introduced the concept of OPPORTUNISTIC ExecutionType.
~~YARN-4335~~ introduced changes to the ResourceRequest so that AMs may request that the Container allocated against the ResourceRequest is of a particular ExecutionType.

This JIRA proposes to provide support for the AM to change the ExecutionType of a previously requested Container.

Attachments

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

YARN-5085.001.patch
05/Dec/16 20:11
178 kB
Arun Suresh
YARN-5085.002.patch
12/Dec/16 22:42
173 kB
Arun Suresh
YARN-5085.002.patch
12/Dec/16 18:10
173 kB
Arun Suresh

Issue Links

contains

YARN-4509 Promote containers from OPPORTUNISTIC to GUARANTEED

Resolved

relates to

YARN-4742 [Umbrella] Enhancements to Distributed Scheduling

Resolved

YARN-5542 Scheduling of opportunistic containers

Resolved

YARN-1197 Support changing resources of an allocated container

Open

Sub-Tasks

1.	Expose API to allow AM to request for change of container ExecutionType	Resolved	Arun Suresh
2.	Refactoring OpportunisticContainerAllocator to use SchedulerRequestKey instead of Priority and other misc fixes	Resolved	Arun Suresh
3.	RM changes to support change of container ExecutionType	Resolved	Arun Suresh
4.	AMRMClient changes to support ExecutionType update	Resolved	Arun Suresh
5.	ContainerManagementProtocol changes to support change of container ExecutionType	Resolved	kartheek muthyala
6.	ContainerScheduler and ContainerManager changes to support ExecType update	Resolved	kartheek muthyala
7.	Clean unused SchedulerRequestKeys once ExecutionType updates are completed	Resolved	Arun Suresh
8.	SchedulerRequestKey compareTo method neglects to compare containerToUpdate	Resolved	Arun Suresh
9.	Add updateContainer API to NMClient.	Resolved	kartheek muthyala
10.	Add flag to notify all types of container updates to NM via NodeHeartbeatResponse	Resolved	kartheek muthyala
11.	Container update RM-NM communication fix for backward compatibility	Resolved	Arun Suresh
12.	Expose UpdateResourceRequest API to allow AM to request for change in container properties	Resolved	Arun Suresh
13.	NMContainerStatus should have the Container ExecutionType.	Resolved	kartheek muthyala
14.	Add documentation for Container Update API	Resolved	Arun Suresh
15.	NM Statestore cleanup for Container updates	Resolved	kartheek muthyala

Activity

People

Assignee:: Arun Suresh

Reporter:: Arun Suresh

Votes:: 0 Vote for this issue

Watchers:: 10 Start watching this issue

Dates

Created:: 13/May/16 20:14

Updated:: 20/Sep/18 18:13

Resolved:: 04/Nov/17 18:04