[
https://issues.apache.org/jira/browse/YARN-5959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15736650#comment-15736650
]
Wangda Tan commented on YARN-5959:
----------------------------------
Look at overall changes and discussed with [~asuresh] offline.
A couple of things we discussed:
1) Currently approach in this patch is, if any normal container request with
higher priority, it will be allocated first. However this is discussable: if we
give the available resource of a node to a different normal container, it is
possible that the running opportunistic container will be killed and work will
be wasted.
2) Instead of creating a hard-locality container request, can we wrap the
ResourceRequest to add some additional information to identify it is for
container increase / promotion. This could be useful for:
- Track pending container changes requests.
- Cancel / update pending container change requests
- Makes backend implementation of container increase / promotion to be same.
- If you think it sounds like a plan, I can also help with working on
refactoring patch / reviews.
> 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.combined.001.patch, YARN-5959.wip.002.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]
