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

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

I see this for YARN-193, using "git blame 
bc6777dd5bdcbaef09897b506bc6511ae456033d"

-  public static final String RM_SCHEDULER_MAXIMUM_ALLOCATION_CORES =
+  public static final String RM_SCHEDULER_MAXIMUM_ALLOCATION_VCORES =
       YARN_PREFIX + "scheduler.maximum-allocation-vcores";
-  public static final int DEFAULT_RM_SCHEDULER_MAXIMUM_ALLOCATION_CORES = 32;
+  public static final int DEFAULT_RM_SCHEDULER_MAXIMUM_ALLOCATION_VCORES = 4;

which looks like moving from 32 to 4 in YarnConfiguration.java while renaming 
_CORES to _VCORES.

I'm not sure if the intended semantics changed during this property rename.  
[~zjshen], [~vinodkv] do either of you have any comment on this?

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

Reply via email to