[
https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294529#comment-14294529
]
Chris Douglas commented on YARN-1039:
-------------------------------------
Requiring accurate estimates is not realistic, but no service runs forever in
the same container(s). If container leases can be renewed/refreshed, that's a
manageable and realistic guarantee for the user (couldn't find a JIRA; it must
exist). Migration, decommission, OS upgrades, and other operations-in-time on
containers seem necessary to support long-running services, since preemption is
comparably heavy-handed. Specifying a precise duration may be a little pedantic
for the existing use cases, but it seems like the right abstraction.
> 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)
