hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hitesh Shah (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-470) Support a way to disable resource monitoring on the NodeManager
Date Wed, 20 Mar 2013 21:31:15 GMT

    [ https://issues.apache.org/jira/browse/YARN-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608248#comment-13608248

Hitesh Shah commented on YARN-470:

   - missing changes in yarn-default.xml 
   - question regarding NodeInfo which reports totalPMem and totalVMem - is the expectation
that it should return the actual configured value or -1 if memory checks are disabled? The
node information sent to the RM in the heartbeat is the actual amount whereas the NM UI seems
to be displaying something else. Does it makes sense to add the memory monitoring flags as
separate bits of information? 
      - this could allow a function like isPhysicalMemoryCheckEnabled to just return the flag
instead of overloading the totalPMemValue when monitoring is disabled. 
   - is this needed: s/YarnConfiguration.DEFAULT_NM_PMEM_MB) * 1024 * 1024/YarnConfiguration.DEFAULT_NM_PMEM_MB)
* 1024 * 1024L/ ? ( missing long qualifier on the last 1024 ) ? 

> 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
>         Attachments: 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

View raw message