[
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-5085.003.patch
Updating patch.
Thanks for the detailed review [~leftnoteasy].
I agree with all your suggestions. I've updated the patch as follows:
# Reverted all changes to the {{AbstractResourceRequest}}. We don't need the
extra {{containerToUpdate}} field anymore, as you pointed out, it was possible
to accomplish everything via the {{SchedulerRequestKey}}
# Modified the call flow remove the update Execution type call from the OCAAMS
and moved it into the Scheduler itself.
# Modified the Allocation object to handle the promoted and demoted containers.
# Split the ContainerUpdateType::UPDATE_EXECUTION_TYPE to
PROMOTE_EXECUTION_TYPE and DEMOTE_EXECUTION_TYPE.
The size of the patch has increased a bit since I modified the allocate()
method of the scheduler to take the promoted and demoted lists. And this
touches a few test classes.
> 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-5085.001.patch,
> YARN-5959-YARN-5085.002.patch, YARN-5959-YARN-5085.003.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]
