[
https://issues.apache.org/jira/browse/YARN-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun Suresh updated YARN-5959:
------------------------------
Attachment: YARN-5959-YARN-5985.001.patch
Updating patch.
* The container increase and decreases accounting has been moved to the
{{AppSchedulingInfo}}.
* To isolate the update code path (and to make it easier to review), i've
created a {{ContainerUpdateContext}} which is field of the
{{AppSchedulingInfo}}. It also encapsulates the datastructures used for
accounting the container increase and decrease.
The new functionality can be used for both ExecutionType Promotion/Demotion as
well as Container resource Increase/Decrease. I have currently just hooked it
to the ExecutionType promote and demote. I feel we should raise another JIRA to
work on removing the existing container increase/decrease code-path and move it
to using the new ContainerUpdateContext.
As with the previous patches, the basic principle is the same.. new
ResourceRequests are created for container increases, but these are created
internally in the {{AppSchedulingInfo}}
[~leftnoteasy], do give it a look.
> RM changes to support change of container ExecutionType
> -------------------------------------------------------
>
> Key: YARN-5959
> URL: https://issues.apache.org/jira/browse/YARN-5959
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Attachments: YARN-5959-YARN-5985.001.patch,
> YARN-5959.combined.001.patch, YARN-5959.wip.002.patch,
> YARN-5959.wip.003.patch, YARN-5959.wip.patch
>
>
> RM side changes to allow an AM to ask for change of ExecutionType.
> Currently, there are two cases:
> # *Promotion* : OPPORTUNISTIC to GUARANTEED.
> # *Demotion* : GUARANTEED to OPPORTUNISTIC.
> This is similar in YARN-1197 which allows for change in Container resources.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
