[
https://issues.apache.org/jira/browse/YARN-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178805#comment-16178805
]
Sunil G commented on YARN-6504:
-------------------------------
Thanks [~dan...@cloudera.com] and [~vvasudev]
I think I could get the reason behind this override capability. Limiting to
memory and cpu sounds good as many of old MR jobs need not have to be
re-written. I have one doubt also here, if one have map.memory-mb or map.vcores
in mapred-site.xml, all MR jobs will now override profile eventhough user
submits the profile in command line. For user, there is no way to know that
this override has happened. I think if we do that, user has to be warned that
map.memory-mb or map.vcores will override profile capability. Thoughts?
> Add support for resource profiles in MapReduce
> ----------------------------------------------
>
> Key: YARN-6504
> URL: https://issues.apache.org/jira/browse/YARN-6504
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager, resourcemanager
> Reporter: Varun Vasudev
> Assignee: Varun Vasudev
> Attachments: YARN-6504-YARN-3926.001.patch,
> YARN-6504.YARN-3926.002.patch, YARN-6504.YARN-3926.003.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
