Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 23 Jun 2014 18:41:28 +0000 (UTC)
From: "Craig Welch (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12662433.1375896184572.30965.1403548888513@arcas>
In-Reply-To: <JIRA.12662433.1375896184572@arcas>
References: <JIRA.12662433.1375896184572@arcas>
Subject: [jira] [Commented] (YARN-1039) Add parameter for YARN resource
 requests to indicate "long lived"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Craig Welch commented on YARN-1039:
-----------------------------------

The more I look around, the better I like the idea of adding it to the resource proto.  It is the same kind of thing as the items already in there - it's a characteristic required for the container (it isn't a metric style quality, but still, it's a characteristic of the resource needed) and it is already present everywhere the information is needed (at application submission and when containers are requested).  Adding something so similar alongside the resource proto seems unnecessary.  Do you agree with [~xgong]'s concerns or do you think it makes sense to add it there?

> 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
>            Priority: Minor
>         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.2#6252)