Craig Welch commented on YARN-1039:

Another thought - if we do need this kind of "flag", I think we should detach 
the notion from duration or "long life" as such - I think it's more about 
service vs batch - where a service's duration is not necessarily related to any 
preset notion of a work item it will start, work on, and complete - it will be 
started to handle work which is given to it, of unknown quantity (& potentially 
many different items) and stopped when no longer needed - it's not so much 
about the duration as the lifecycle (a batch operation may have a longer 
runtime than a service, for example).  So, I'd suggest dropping the "temporal" 
flavor and going with "service" vs "batch", or something along those lines.

> 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

Reply via email to