[
https://issues.apache.org/jira/browse/YARN-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799772#comment-15799772
]
Arun Suresh edited comment on YARN-5959 at 1/5/17 12:06 AM:
------------------------------------------------------------
Updated patch. Do give it another review [~leftnoteasy]
bq. Can we make scheduler.allocate to have a single ContainerUpdateRequests,
which include 4 lists (increase/decrease/promotion/demotion) instead of making
all of them become top-level parameter, similarly for Allocation.
I've created a holder class ContainerUpdateContext.ContainerUpdateRequests
which is created in the RMServerUtils#validate.. method and passed around.
I don't think we need one for the Allocation object, since technically, it
itself is a holder for all the lists of allocated/updated containers.
Agree to all other suggestions, and its incorporated in the patch.
was (Author: asuresh):
Updated patch. Do give it another review [~leftnoteasy]
bq. Can we make scheduler.allocate to have a single ContainerUpdateRequests,
which include 4 lists (increase/decrease/promotion/demotion) instead of making
all of them become top-level parameter, similarly for Allocation.
I've created a holder class ContainerUpdateContext.ContainerUpdateRequests
which is created in the RMServerUtils#validate.. method and passed around.
I don't think we need one for the Allocation object, since technically, it
itself is a holder for all the lists.
Agree to all other suggestions, and its incorporated in the patch.
> 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-YARN-5085.004.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]
