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 "Miklos Szegedi (JIRA)" <ji...@apache.org> on 2017/11/20 22:15:00 UTC
[jira] [Commented] (YARN-6750) Add a configuration to cap how much
a NM can be overallocated
[ https://issues.apache.org/jira/browse/YARN-6750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259942#comment-16259942 ]
Miklos Szegedi commented on YARN-6750:
--------------------------------------
Thank you for the patch [~haibochen].
{code}
99
100 public SchedulerNode(RMNode node, boolean usePortForNodeName,
{code}
There is an extra space here.
All references to 4.0 in the patch should be replaced with YarnConfiguration.DEFAULT_PER_NODE_MAX_OVERALLOCATION_RATIO.
> Add a configuration to cap how much a NM can be overallocated
> -------------------------------------------------------------
>
> Key: YARN-6750
> URL: https://issues.apache.org/jira/browse/YARN-6750
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager
> Reporter: Haibo Chen
> Assignee: Haibo Chen
> Attachments: YARN-6750-YARN-1011.00.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org