[
https://issues.apache.org/jira/browse/YARN-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15330116#comment-15330116
]
Roni Burd commented on YARN-5085:
---------------------------------
Regarding:
I see the need for a promotion, why would we want to demote?
A couple of scenarios come comes to mind
1) long running processes - a user may temporary upgrade some tokens to catch
up after a live site or deal with an important skew with and event.
2) A distributed scheduled or RM may race some containers to make a deadline or
to optimize latency in the face of limited containers in their queue. Demotion
is basically a way to flip some container from OP -> GUA and another from GUA
-> OP and preserving the queue limit.
> Add support for change of container ExecutionType
> -------------------------------------------------
>
> Key: YARN-5085
> URL: https://issues.apache.org/jira/browse/YARN-5085
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Arun Suresh
> Assignee: Arun Suresh
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
