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 8E3E818C99 for ; Mon, 25 Jan 2016 04:00:47 +0000 (UTC) Received: (qmail 64394 invoked by uid 500); 25 Jan 2016 04:00:42 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 64291 invoked by uid 500); 25 Jan 2016 04:00:42 -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 64263 invoked by uid 99); 25 Jan 2016 04:00:42 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jan 2016 04:00:42 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 247F12C1F62 for ; Mon, 25 Jan 2016 04:00:42 +0000 (UTC) Date: Mon, 25 Jan 2016 04:00:42 +0000 (UTC) From: "Kai Sasaki (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4499) Bad config values of "yarn.scheduler.maximum-allocation-vcores" 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-4499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114718#comment-15114718 ] Kai Sasaki commented on YARN-4499: ---------------------------------- The issue seems to be already fixed by YARN-3823. > Bad config values of "yarn.scheduler.maximum-allocation-vcores" > --------------------------------------------------------------- > > Key: YARN-4499 > URL: https://issues.apache.org/jira/browse/YARN-4499 > Project: Hadoop YARN > Issue Type: Bug > Components: scheduler > Affects Versions: 2.7.1, 2.6.2 > Reporter: Tianyin Xu > > Currently, the default value of {{yarn.scheduler.maximum-allocation-vcores}} is {{32}}, according to [yarn-default.xml|https://hadoop.apache.org/docs/r2.7.1/hadoop-yarn/hadoop-yarn-common/yarn-default.xml]. > However, in {{YarnConfiguration.java}}, we specify the default to be {{4}}. > {code} > public static final String RM_SCHEDULER_MAXIMUM_ALLOCATION_VCORES = > YARN_PREFIX + "scheduler.maximum-allocation-vcores"; > public static final int DEFAULT_RM_SCHEDULER_MAXIMUM_ALLOCATION_VCORES = 4; > {code} > The default in the code looks correct to me. Actually I feel that the default value should be the same as {{yarn.nodemanager.resource.cpu-vcores}} (whose default is {{8}}) ---if we have {{8}} cores for scheduling, there's few reason we only allow the maximum of {{4}}... > The Cloudera's article on [Tuning the Cluster for MapReduce v2 (YARN) |http://www.cloudera.com/content/www/en-us/documentation/enterprise/5-3-x/topics/cdh_ig_yarn_tuning.html] also suggests that "the maximum value ( {{yarn.scheduler.maximum-allocation-vcores}}) is usually equal to {{yarn.nodemanager.resource.cpu-vcores}}..." > At the very least, we should fix [yarn-default.xml|https://hadoop.apache.org/docs/r2.7.1/hadoop-yarn/hadoop-yarn-common/yarn-default.xml]. The error is pretty bad. A simple search on the Internet shows some ppl are confused by this error, for example, > https://community.cloudera.com/t5/Cloudera-Manager-Installation/yarn-nodemanager-resource-cpu-vcores-and-yarn-scheduler-maximum/td-p/31098 > \\ > (but seriously, I think we should have an automatic defaults with the min as 1 and the max equal to the number of cores on the machine... -- This message was sent by Atlassian JIRA (v6.3.4#6332)