[
https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298135#comment-14298135
]
Chris Douglas commented on YARN-1039:
-------------------------------------
bq. That's not necessarily so, there are some cases where the type of life
cycle for an application is important, for example, when determining whether or
not it is open-ended ("service") or a batch process which entails a notion of
progress ("session"), at least for purposes of display.
That's a fair distinction. Would you agree the YARN _scheduler_ should not use
detailed information about progress, task dependencies, or service lifecycles?
If an AM registers with a tag that affects the attributes displayed in
dashboards, then issues like YARN-1079 can be resolved cleanly, as you and
Zhijie propose.
Steve has a point about mixed-mode AMs that run both long and short-lived
containers (e.g., a long-lived service supporting a workflow composed of short
tasks). If it's solely for display, then an enum seems adequate, but I'd like
to better understand the use cases.
> 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)
