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

Steve Loughran commented on YARN-1039:
--------------------------------------

+1 for a long-lived bit. Services can set the flag, and it is up for future 
versions of Hadoop to implement the logic to go with it. 

FWIW, I'd make the first use of the patch the YARN-1079 progress bar. 

Why? it's the least amount of server-side code changes (no scheduling patches), 
it fixes a tangible problem for users (progress bar is confusing), and it 
provides an immediate benefit to the apps —so encouraging them to set the flag, 
maybe even by reflection if they want to stay compatible across hadoop versions.

> 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