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 276E911C54 for ; Mon, 25 Aug 2014 19:31:01 +0000 (UTC) Received: (qmail 59641 invoked by uid 500); 25 Aug 2014 19:31:01 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 59604 invoked by uid 500); 25 Aug 2014 19:31:01 -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 59592 invoked by uid 99); 25 Aug 2014 19:31:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Aug 2014 19:31:00 +0000 Date: Mon, 25 Aug 2014 19:31:00 +0000 (UTC) From: "Karthik Kambatla (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-2448) RM should expose the name of the ResourceCalculator being used when AMs register 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-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109603#comment-14109603 ] Karthik Kambatla commented on YARN-2448: ---------------------------------------- May be I am missing your point. Why not have the MR AM request both CPU and memory? If the RM/scheduler doesn't consider CPU, it will just ignore it. Related, but orthogonal point: In the case of FairScheduler, the policy depends on the queue the app is submitted to. So, some queues might consider only CPU, some only memory, and some both. So, exposing the ResourceCalculator doesn't really tell the AM anything, it has to look at the queue configuration. > RM should expose the name of the ResourceCalculator being used when AMs register > -------------------------------------------------------------------------------- > > Key: YARN-2448 > URL: https://issues.apache.org/jira/browse/YARN-2448 > Project: Hadoop YARN > Issue Type: Improvement > Reporter: Varun Vasudev > Assignee: Varun Vasudev > Attachments: apache-yarn-2448.0.patch, apache-yarn-2448.1.patch > > > The RM should expose the name of the ResourceCalculator being used when AMs register, as part of the RegisterApplicationMasterResponse. > This will allow applications to make better decisions when scheduling. MapReduce for example, only looks at memory when deciding it's scheduling, even though the RM could potentially be using the DominantResourceCalculator. -- This message was sent by Atlassian JIRA (v6.2#6252)