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

Hudson commented on YARN-1046:
------------------------------

SUCCESS: Integrated in Hadoop-Yarn-trunk #297 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/297/])
YARN-1046. Disable mem monitoring my default in MiniYARNCluster (Karthik 
Kambatla via Sandy Ryza) (sandy: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1512493)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/src/main/java/org/apache/hadoop/yarn/conf/YarnConfiguration.java
* 
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-tests/src/test/java/org/apache/hadoop/yarn/server/MiniYARNCluster.java

                
> Disable mem monitoring by default in MiniYARNCluster
> ----------------------------------------------------
>
>                 Key: YARN-1046
>                 URL: https://issues.apache.org/jira/browse/YARN-1046
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.1.0-beta
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>             Fix For: 2.1.0-beta
>
>         Attachments: yarn-1046-1.patch, yarn-1046-2.patch
>
>
> Have been running into this frequently inspite of MAPREDUCE-3709 on centos6 
> machines. However, when I try to run it independently on the machines, I have 
> not been able to reproduce it.
> {noformat}
> 2013-08-07 19:17:35,048 WARN  [Container Monitor] 
> monitor.ContainersMonitorImpl (ContainersMonitorImpl.java:run(444)) - 
> Container [pid=16556,containerID=container_1375928243488_0001_01_000001] is 
> running beyond virtual memory limits. Current usage: 132.4 MB of 512 MB 
> physical memory used; 1.2 GB of 1.0 GB virtual memory used. Killing container.
> {noformat}

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

Reply via email to