Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 4 Apr 2013 21:36:15 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12636699.1363136178838.110629.1365111375729@arcas>
In-Reply-To: <JIRA.12636699.1363136178838@arcas>
References: <JIRA.12636699.1363136178838@arcas>
Subject: [jira] [Commented] (YARN-470) Support a way to disable resource
 monitoring on the NodeManager
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on YARN-470:
-----------------------------

Integrated in Hadoop-trunk-Commit #3565 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3565/])
    Updated CHANGES.txt to reflect YARN-470 being merged into branch-2.0.4-alpha. (Revision 1464772)

     Result = SUCCESS
sseth : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1464772
Files : 
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt

                
> 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