You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/07/01 07:57:05 UTC
[jira] [Commented] (YARN-3823) Fix mismatch in default values for
yarn.scheduler.maximum-allocation-vcores property
[ https://issues.apache.org/jira/browse/YARN-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14609599#comment-14609599 ]
Hudson commented on YARN-3823:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #8104 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8104/])
YARN-3823. Fix mismatch in default values for (devaraj: rev 7405c59799ed1b8ad1a7c6f1b18fabf49d0b92b2)
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml
* hadoop-yarn-project/CHANGES.txt
> Fix mismatch in default values for yarn.scheduler.maximum-allocation-vcores property
> ------------------------------------------------------------------------------------
>
> Key: YARN-3823
> URL: https://issues.apache.org/jira/browse/YARN-3823
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.7.0
> Reporter: Ray Chiang
> Assignee: Ray Chiang
> Priority: Minor
> Labels: supportability
> Fix For: 2.8.0
>
> Attachments: YARN-3823.001.patch, YARN-3823.002.patch
>
>
> In yarn-default.xml, the property is defined as:
> XML Property: yarn.scheduler.maximum-allocation-vcores
> XML Value: 32
> In YarnConfiguration.java the corresponding member variable is defined as:
> Config Name: DEFAULT_RM_SCHEDULER_MAXIMUM_ALLOCATION_VCORES
> Config Value: 4
> The Config value comes from YARN-193 and the default xml property comes from YARN-2. Should we keep it this way or should one of the values get updated?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)