[
https://issues.apache.org/jira/browse/YARN-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740657#comment-13740657
]
Alejandro Abdelnur commented on YARN-1064:
------------------------------------------
The ones that caught my eye are:
{code}
YARN_PREFIX + "scheduler.minimum-allocation-mb";
YARN_PREFIX + "scheduler.minimum-allocation-vcores";
YARN_PREFIX + "scheduler.maximum-allocation-mb";
YARN_PREFIX + "scheduler.maximum-allocation-vcores";
RM_PREFIX + "scheduler.client.thread-count";
RM_PREFIX + "scheduler.monitor.enable";
RM_PREFIX + "scheduler.monitor.policies";
{code}
YARN-1004 would take care of the first 2. What about the last 3, are they a
false positive from my side and it is OK they say in the RM? If so, we can
close this as invalid.
> YarnConfiguration scheduler configuration constants are not consistent
> ----------------------------------------------------------------------
>
> Key: YARN-1064
> URL: https://issues.apache.org/jira/browse/YARN-1064
> Project: Hadoop YARN
> Issue Type: Bug
> Components: scheduler
> Affects Versions: 2.1.0-beta
> Reporter: Alejandro Abdelnur
> Priority: Blocker
> Labels: newbie
> Fix For: 2.1.0-beta
>
>
> Some of the scheduler configuration constants in YarnConfiguration have
> RM_PREFIX and others YARN_PREFIX. For consistency we should move all under
> the same prefix.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
