Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2637D200BB7 for ; Wed, 26 Oct 2016 01:04:00 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 24CB5160AFA; Tue, 25 Oct 2016 23:04:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 6AB65160AD8 for ; Wed, 26 Oct 2016 01:03:59 +0200 (CEST) Received: (qmail 23855 invoked by uid 500); 25 Oct 2016 23:03:58 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 23840 invoked by uid 99); 25 Oct 2016 23:03:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Oct 2016 23:03:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 62B5A2C2A68 for ; Tue, 25 Oct 2016 23:03:58 +0000 (UTC) Date: Tue, 25 Oct 2016 23:03:58 +0000 (UTC) From: "Arun Suresh (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-5587) Add support for resource profiles MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 25 Oct 2016 23:04:00 -0000 [ https://issues.apache.org/jira/browse/YARN-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606739#comment-15606739 ] Arun Suresh commented on YARN-5587: ----------------------------------- I feel we should try to keep this simple. Given that we have already introduced a {{ProfileCapability}} class that takes a profile name and a possible Capability override, I propose: # We create a special {{ProfileCapability}} with profile name *NONE* where user only specifies the capability (Resource). This would be equivalent to our old {{Resource}} # We replace the capability(Resource) argument in both the {{ContainerRequest}} and {{ResourceRequest}} with {{ProfileCapability}}. Maybe for backward compatibility, we have 1 constructor that takes Resource and 1 that takes ProfileCapability. We then convert a Resource to ProfileCapability(NONE, Resource) in the AMRMClient. # In the rest of the {{AMRMClient}} codebase, including the {{RemoteRequestsTable} }we just use {{ProfileCapability}} > Add support for resource profiles > --------------------------------- > > Key: YARN-5587 > URL: https://issues.apache.org/jira/browse/YARN-5587 > Project: Hadoop YARN > Issue Type: Sub-task > Components: nodemanager, resourcemanager > Reporter: Varun Vasudev > Assignee: Varun Vasudev > Attachments: YARN-5587-YARN-3926.001.patch, YARN-5587-YARN-3926.002.patch, YARN-5587-YARN-3926.003.patch, YARN-5587-YARN-3926.004.patch, YARN-5587-YARN-3926.005.patch > > > Add support for resource profiles on the RM side to allow users to use shorthands to specify resource requirements. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org