Jian Fang commented on YARN-1039:

The term "long lived" relies on resource manager to understand what "long 
lived" means. How to define that in resource manager then? Do you still rely on 
node managers to provide tags/labels and resource manager to understand them? 
If that is true, shouldn't YARN-796 have already addressed this issue with a 
more generic way to schedule containers based on tags/labels? 

Personally, I think YARN-796 is more generic. Take the spot instance mentioned 
here as an example, customers don't want to schedule AM containers on spot 
instances as well, not just long lived tasks. 

> 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