[ https://issues.apache.org/jira/browse/YARN-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735402#comment-13735402 ]
Karthik Kambatla commented on YARN-1046: ---------------------------------------- [~hitesh], I was wondering the same. In the end, just followed what MAPREDUCE-5094 did. It does make sense to only disable vmem monitoring. Also, we shouldn't need to do MAPREDUCE-5094 any more. Should I post an addendum that does all this or file a new JIRA? > 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