Sunil G commented on YARN-1039:

"duration" is a better metric than token names. However to reach to this 
"duration" metric, few trail runs for application is needed OR new container 
requests can be raised by AM based on its previous containers running time.

So a feedback mechanism to AM is coming alive here from RMs perspective, like 
AM is supposed to run a container for so long duration, but since as the limit 
is crossed, AM can take some action. I feel this will add a good amount 

> 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