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 "Siddharth Seth (JIRA)" <ji...@apache.org> on 2013/04/04 23:24:16 UTC
[jira] [Updated] (YARN-470) Support a way to disable resource
monitoring on the NodeManager
[ https://issues.apache.org/jira/browse/YARN-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Seth updated YARN-470:
--------------------------------
Fix Version/s: (was: 2.0.5-beta)
2.0.4-alpha
Pulled this into 2.0.4-alpha, so that MiniMRCluster resource monitoring can be controlled by downstream projects.
> Support a way to disable resource monitoring on the NodeManager
> ---------------------------------------------------------------
>
> Key: YARN-470
> URL: https://issues.apache.org/jira/browse/YARN-470
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Reporter: Hitesh Shah
> Assignee: Siddharth Seth
> Labels: usability
> Fix For: 2.0.4-alpha
>
> Attachments: YARN-470_2.txt, YARN-470.txt
>
>
> Currently, the memory management monitor's check is disabled when the maxMem is set to -1. However, the maxMem is also sent to the RM when the NM registers with it ( to define the max limit of allocate-able resources ).
> We need an explicit flag to disable monitoring to avoid the problems caused by the overloading of the max memory value.
--
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