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 "lovekesh bansal (JIRA)" <ji...@apache.org> on 2018/02/14 06:13:00 UTC
[jira] [Assigned] (YARN-7328) ResourceUtils allows
yarn.nodemanager.resource-types.memory-mb and .vcores to override
yarn.nodemanager.resource.memory-mb and .cpu-vcores
[ https://issues.apache.org/jira/browse/YARN-7328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
lovekesh bansal reassigned YARN-7328:
-------------------------------------
Assignee: lovekesh bansal
> ResourceUtils allows yarn.nodemanager.resource-types.memory-mb and .vcores to override yarn.nodemanager.resource.memory-mb and .cpu-vcores
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: YARN-7328
> URL: https://issues.apache.org/jira/browse/YARN-7328
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager
> Affects Versions: 3.1.0
> Reporter: Daniel Templeton
> Assignee: lovekesh bansal
> Priority: Critical
> Attachments: YARN-7328_trunk.001.patch
>
>
> We will throw an exception if yarn.nodemanager.resource-types.memory is configured, but not if .memory-mb or .vcores is configured. We should be consistent. We should not allow resource types to redefine something for which we already have a property to set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org