[
https://issues.apache.org/jira/browse/HADOOP-8603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Katsov resolved HADOOP-8603.
---------------------------------
Resolution: Duplicate
Moved to https://issues.apache.org/jira/browse/MAPREDUCE-4535
> Test failures with "Container .. is running beyond virtual memory limits"
> -------------------------------------------------------------------------
>
> Key: HADOOP-8603
> URL: https://issues.apache.org/jira/browse/HADOOP-8603
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
> Affects Versions: 0.23.3
> Environment: CentOS 6.2
> Reporter: Ilya Katsov
> Labels: test
> Attachments: HADOOP-8603-branch-0.23.patch,
> HADOOP-8603-branch-0.23_002.patch
>
>
> Tests
> org.apache.hadoop.tools.TestHadoopArchives.{testRelativePath,testPathWithSpaces}
> fail with the following message:
> {code}
> Container [pid=7785,containerID=container_1342495768864_0001_01_000001] is
> running beyond virtual memory limits. Current usage: 143.6mb of 1.5gb
> physical memory used; 3.4gb of 3.1gb virtual memory used. Killing container.
> Dump of the process-tree for container_1342495768864_0001_01_000001 :
> |- PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS)
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE
> |- 7797 7785 7785 7785 (java) 573 38 3517018112 36421
> /usr/java/jdk1.6.0_33/jre/bin/java
> -Dlog4j.configuration=container-log4j.properties
> -Dyarn.app.mapreduce.container.log.dir=/var/lib/jenkins/workspace/Hadoop_gd-branch0.23_integration/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/target/org.apache.hadoop.mapred.MiniMRCluster/org.apache.hadoop.mapred.MiniMRCluster-logDir-nm-0_3/application_1342495768864_0001/container_1342495768864_0001_01_000001
> -Dyarn.app.mapreduce.container.log.filesize=0 -Dhadoop.root.logger=INFO,CLA
> -Xmx1024m org.apache.hadoop.mapreduce.v2.app.MRAppMaster
> |- 7785 7101 7785 7785 (bash) 1 1 108605440 332 /bin/bash -c
> /usr/java/jdk1.6.0_33/jre/bin/java
> -Dlog4j.configuration=container-log4j.properties
> -Dyarn.app.mapreduce.container.log.dir=/var/lib/jenkins/workspace/Hadoop_gd-branch0.23_integration/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/target/org.apache.hadoop.mapred.MiniMRCluster/org.apache.hadoop.mapred.MiniMRCluster-logDir-nm-0_3/application_1342495768864_0001/container_1342495768864_0001_01_000001
> -Dyarn.app.mapreduce.container.log.filesize=0 -Dhadoop.root.logger=INFO,CLA
> -Xmx1024m org.apache.hadoop.mapreduce.v2.app.MRAppMaster
> 1>/var/lib/jenkins/workspace/Hadoop_gd-branch0.23_integration/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/target/org.apache.hadoop.mapred.MiniMRCluster/org.apache.hadoop.mapred.MiniMRCluster-logDir-nm-0_3/application_1342495768864_0001/container_1342495768864_0001_01_000001/stdout
>
> 2>/var/lib/jenkins/workspace/Hadoop_gd-branch0.23_integration/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/target/org.apache.hadoop.mapred.MiniMRCluster/org.apache.hadoop.mapred.MiniMRCluster-logDir-nm-0_3/application_1342495768864_0001/container_1342495768864_0001_01_000001/stderr
>
> {code}
> Is it related to https://issues.apache.org/jira/browse/MAPREDUCE-3933 ? This
> is not a stably reproducible problem, but it seems that adding
> MALLOC_ARENA_MAX resolves the problem.
--
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
