[ 
https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043238#comment-14043238
 ] 

Wangda Tan commented on YARN-1039:
----------------------------------

bq. it must be set at application creation time and all containers of the app 
will be considered long lived. This is because the RM does not keep track of 
individual container requests.
I think [~vinodkv]'s suggestion makes more sense to me: 
https://issues.apache.org/jira/browse/YARN-1039?focusedCommentId=14041652&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14041652
And as [~cwelch] mentioned, we don't need constraint if an app is long-lived 
that all its containers should be long-lived, it's better to leave this 
decision to app itself.

> Add parameter for YARN resource requests to indicate "long lived"
> -----------------------------------------------------------------
>
>                 Key: YARN-1039
>                 URL: https://issues.apache.org/jira/browse/YARN-1039
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 3.0.0, 2.1.1-beta
>            Reporter: Steve Loughran
>            Assignee: Craig Welch
>         Attachments: YARN-1039.1.patch, YARN-1039.2.patch, YARN-1039.3.patch
>
>
> A container request could support a new parameter "long-lived". This could be 
> used by a scheduler that would know not to host the service on a transient 
> (cloud: spot priced) node.
> Schedulers could also decide whether or not to allocate multiple long-lived 
> containers on the same node



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to