[
https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294557#comment-14294557
]
Craig Welch commented on YARN-1039:
-----------------------------------
[~chris.douglas] what's the proper duration for a service which does not have a
pre-defined lifetime?
This distinction is not really about "how long will it run" but more about
"what is the lifecycle of this app" - as [[email protected]] points out, is it
session or batch oriented (something which has a defined set of work, so it has
a notion of progress to completion) or is it a running process with an
indeterminate/unknown lifetime which handles whatever work is sent it's way (a
service). This is really the distinction needed here - it's a qualitative
difference regarding a lifecycle, the notion of an enumeration of lifecycle
types makes sense for this. Users will often have no idea how long their
application will run, but they will generally have a clear notion of it's
lifecycle.
> 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)
