[ https://issues.apache.org/jira/browse/MAPREDUCE-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ahmed Radwan updated MAPREDUCE-3933: ------------------------------------ Attachment: MAPREDUCE-3933.patch A patch setting MALLOC_ARENA_MAX in the root pom.xml. I also removed this setting from DistributedShell pom as it is no longer needed when it is added to the root pom. I have verified that all failing tests now run successfully. > Failures because MALLOC_ARENA_MAX is not set > -------------------------------------------- > > Key: MAPREDUCE-3933 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3933 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2, test > Affects Versions: 0.23.0 > Reporter: Ahmed Radwan > Assignee: Ahmed Radwan > Attachments: MAPREDUCE-3933.patch > > > We have noticed a bunch of MapReduce test failures on CentOS 6 due to > "running beyond virtual memory limits". > These tests fail with messages of the form: > {code} > [Node Status Updater] nodemanager.NodeStatusUpdaterImpl > (NodeStatusUpdaterImpl.java:getNodeStatus(254)) - Sending out status for > container: container_id {, app_attempt_id {, application_id {, id: 1, > cluster_timestamp: 1330401645767, }, attemptId: 1, }, id: 1, }, state: > C_RUNNING, diagnostics: "Container > [pid=16750,containerID=container_1330401645767_0001_01_000001] is running > beyond virtual memory limits. Current usage: 220.5mb of 2.0gb physical memory > used; 7.1gb of 4.2gb virtual memory used. Killing container > {code} > The failing tests are: > {code} > TestJobCounters > TestJobSysDirWithDFS > TestLazyOutput > TestMiniMRChildTask > TestMiniMRClientCluster > TestReduceFetchFromPartialMem > TestChild > TestMapReduceLazyOutput > TestJobOutputCommitter > TestMRAppWithCombiner > TestMRJobs > TestMRJobsWithHistoryService > TestMROldApiJobs > TestSpeculativeExecution > TestUberAM > {code} > I'll upload a patch momentarily. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira