hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlo Curino (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1039) Add parameter for YARN resource requests to indicate "long lived"
Date Tue, 01 Jul 2014 00:15:26 GMT

    [ https://issues.apache.org/jira/browse/YARN-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048345#comment-14048345

Carlo Curino commented on YARN-1039:

Hi Guys, I am just tuning in now... (apologies if I am misinterpreting the conversation),
but it seems that some of the proposed changes resemble what we were proposing for the reservation
YARN-1051 work. In the sub-task YARN-1708 we propose and extension of ResourceRequest that
expresses the "duration" (or leaseDuration if you prefer) for which resources will be reserved...
The same concept could be used here as a hint from the user on "for how long I expect to hold
onto the resources". What I am suggesting is that having a "time" associated with a ResourceRequest
could serve both purposes, and be a generally useful hint to the RM.


> 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

View raw message