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 "Devaraj K (JIRA)" <ji...@apache.org> on 2015/07/01 07:36:05 UTC

[jira] [Updated] (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:all-tabpanel ]

Devaraj K updated YARN-3823:
----------------------------
    Hadoop Flags: Reviewed

Thanks [~zjshen] for confirmation.

+1 for the latest patch. 

> 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
>         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)