Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C18F318BFC for ; Tue, 5 Jan 2016 22:00:42 +0000 (UTC) Received: (qmail 76732 invoked by uid 500); 5 Jan 2016 22:00:41 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 76562 invoked by uid 500); 5 Jan 2016 22:00:41 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 76285 invoked by uid 99); 5 Jan 2016 22:00:41 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jan 2016 22:00:41 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 273682C1F72 for ; Tue, 5 Jan 2016 22:00:41 +0000 (UTC) Date: Tue, 5 Jan 2016 22:00:41 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4335) Allow ResourceRequests to specify ExecutionType of a request ask MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083919#comment-15083919 ] Wangda Tan commented on YARN-4335: ---------------------------------- Thanks [~kkaranasos] for updating the patch bq. Just double-checking: do you mean adding an additional description in the javadoc of the ExecutionType? Yes And: {code} 87 @Public 88 @Stable 89 public static ResourceRequest newInstance(Priority priority, String hostName, ... {code} Should be unstable as well. As [~kasha] [commented|https://issues.apache.org/jira/browse/YARN-1011?focusedCommentId=15076749&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15076749] on YARN-1011: bq. Given this complication, I would prefer we do not involve AMs in the decision-making process. Based on the need and usecases, we could revisit this at a later time. Note that YARN-4335 adds this to ResourceRequest for distributed scheduling, and even there they are not entirely sure if it needs to be a part. I'm not sure if there's any tasks of YARN-2877 directly depends on it, It's fine to me to commit this to YARN-2877 branch, but I prefer to hold commit unless any tasks require it. > Allow ResourceRequests to specify ExecutionType of a request ask > ---------------------------------------------------------------- > > Key: YARN-4335 > URL: https://issues.apache.org/jira/browse/YARN-4335 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager, resourcemanager > Reporter: Konstantinos Karanasos > Assignee: Konstantinos Karanasos > Attachments: YARN-4335-yarn-2877.001.patch, YARN-4335.002.patch > > > YARN-2882 introduced container types that are internal (not user-facing) and are used by the ContainerManager during execution at the NM. > With this JIRA we are introducing (user-facing) resource request types that are used by the AM to specify the type of the ResourceRequest. > We will initially support two resource request types: CONSERVATIVE and OPTIMISTIC. > CONSERVATIVE resource requests will be handed internally to containers of GUARANTEED type, whereas OPTIMISTIC resource requests will be handed to QUEUEABLE containers. -- This message was sent by Atlassian JIRA (v6.3.4#6332)