Craig Welch commented on YARN-1039:

I'll go back to my earlier assertion that I think it's not "duration" we are 
really concerned with here, that is covered in various ways in other places, 
but more the notion of an application type, a "batch" or a "service", with the 
defining characteristic being for the potential of "continuous operation" 
(service) or "unit of work which will run to completion" (batch), and an 
enumeration of "service" and "batch" make sense to me.  In any case, 
[~vinodkv], it seems that there still seems to be enough diversity of opinion 
here to require some ongoing discussion/reconciliation, so I will leave this in 
your capable hands.

> 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: Vinod Kumar Vavilapalli
>         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