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

Jian Fang commented on YARN-1039:
---------------------------------

The container request could specify what tags/labels it requires, right? 
Tag/label is not really a resource but an attribute instead IMO, just like 
short lived and long lived. 

Even you could specify long-live or short-live, resource manager still needs to 
translate that into something meaningful, right? Or do you say that you have 
some specific logic in YARN to handle the "long lived" containers? If that is 
true, then it is a different story. Could you please elaborate a bit more about 
how "long lived" is defined in YARN and what kinds of specific handling there? 
Thanks.

> 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.3.4#6332)

Reply via email to