hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ray Chiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3823) Fix mismatch in default values for yarn.scheduler.maximum-allocation-vcores property
Date Tue, 30 Jun 2015 18:55:04 GMT

    [ https://issues.apache.org/jira/browse/YARN-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608864#comment-14608864
] 

Ray Chiang commented on YARN-3823:
----------------------------------

That makes sense.  I'll update yarn-default.xml to match YarnConfiguration.DEFAULT_RM_SCHEDULER_MAXIMUM_ALLOCATION_VCORES
then.  Thanks!

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

Mime
View raw message