Carlo Curino commented on YARN-1039:

I agree this conversation floated all-over the map. Thanks for instigating 

I favor the "duration" as it easily covers the boolean use-case, and gives us a 
little extra information bandwidth (i.e., accomodates few upcoming usecases 
with no changes). 
However, I understand where the pushback would come from, and I can't argue too 
much against keeping things more minimal to start. 

> 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