[
https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284104#comment-14284104
]
Carlo Curino commented on YARN-1039:
------------------------------------
I am happy the conversation is re-ignited. As I was mentioning in [above |
https://issues.apache.org/jira/browse/YARN-1039?focusedCommentId=14048345&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14048345],
the "long-lived" tag is a coarse grained version of the notion of "duration"
we added to the ReservationRequest (which tracks very closely ResourceRequest)
in YARN-1051.
The idea is that the AM could provide an estimate of the task duration,
enabling (beyond what Steve already listed above) optimistic scheduling
decisions like the one in YARN-2877 very short tasks (we run several
experiments and the potential for increased utilization is substantial). Given
a "duration" parameter, expressing long-lived can be done by setting duration
to a large value (or MAX_INT, or -1 or whatever convention).
> 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
(v6.3.4#6332)
