Craig Welch commented on YARN-1039:

Not to make things overly complex, but we were talking about making this an 
enum rather than a simple boolean, with the notion that this is one of a number 
of possible "scheduler hints" we may want to support - with values like 
PERSISTENT, TRANSIENT, RELOCATABLE, etc (a single value or possibly a list/set 
of values, for cases which are not mutually exclusive).  Thoughts? 

> 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
>            Priority: Minor
> 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