Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 22 Mar 2013 21:05:15 +0000 (UTC)
From: "Siddharth Seth (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12638571.1363979593481.39607.1363986315560@arcas>
In-Reply-To: <JIRA.12638571.1363979593481@arcas>
References: <JIRA.12638571.1363979593481@arcas>
Subject: [jira] [Commented] (MAPREDUCE-5094) Disable mem monitoring by
 default in MiniMRYarnCluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Siddharth Seth commented on MAPREDUCE-5094:
-------------------------------------------

Killed for exceeding vmem. PMEM is <300MB iirc, vmem going over 6GB - ideally, this should be investigated further.

For now, proposing changing behaviour for MiniMRCluster memory monitoring back to what it was in 1.x (my guess is enabling the mem checks in 1.x would cause the same behaviour).
                
> Disable mem monitoring by default in MiniMRYarnCluster
> ------------------------------------------------------
>
>                 Key: MAPREDUCE-5094
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5094
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Siddharth Seth
>            Assignee: Siddharth Seth
>
> YARN-449. Some hbase tests were failing since containers were getting killed. 
> I believe these checks are disabled by default on the branch-1 MiniMRCluster.

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