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

Vladimir Prus commented on OOZIE-3307:
--------------------------------------

I am not sure where Ozzie sets the options, I was looking at the processes with 
"ps". E.g. I have Ooozie 4, its starts a launcher as 
container_1532455670006_41980_01_000001, the first line of the log is "Oozie 
Launcher starts", and "ps" output is this:
{code:java}
yarn     17649 17647  0 10:18 ?        00:00:00 /bin/bash -c 
/usr/lib/jvm/java-openjdk/bin/java 
-Djava.io.tmpdir=/mnt1/yarn/usercache/hadoop/appcache/application_1532455670006_41980/container_1532455670006_41980_01_000001/tmp
 -Dlog4j.configuration=container-log4j.properties 
-Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1532455670006_41980/container_1532455670006_41980_01_000001
 -Dyarn.app.container.log.filesize=0 -Dhadoop.root.logger=INFO,CLA 
-Dhadoop.root.logfile=syslog  -Xmx4685m -Xmx200m -Xmx2342m -Xmx5197m 
-Djava.io.tmpdir=./tmp org.apache.hadoop.mapreduce.v2.app.MRAppMaster 
1>/var/log/hadoop-yarn/containers/application_1532455670006_41980/container_1532455670006_41980_01_000001/stdout
 
2>/var/log/hadoop-yarn/containers/application_1532455670006_41980/container_1532455670006_41980_01_000001/stderr{code}
Doing the same on cluster with Oozie 5 does not show any -Xmx options.

 

The code that seems relevant is at 
[https://github.com/apache/oozie/blob/3d0843260199799be634dc330d98f1362536fcd5/core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java#L402]

This code appears removed in master. setJavaOpts will only set options provided 
in <launcher> element explicitly, and I see no code that would set Xmx 
automatically.

 

> oozie workflow gets failed throwing error virtual memory limits
> ---------------------------------------------------------------
>
>                 Key: OOZIE-3307
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3307
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: 5.0.0
>            Reporter: Sabir Naikwadi
>            Priority: Critical
>
> Application application_1531909575787_0039 failed 2 times due to AM Container 
> for appattempt_1531909575787_0039_000002 exited with exitCode: -103
>  Failing this attempt.Diagnostics: Container 
> [pid=11516,containerID=container_1531909575787_0039_02_000001] is running 
> beyond virtual memory limits. Current usage: 469.8 MB of 2 GB physical memory 
> used; 10.0 GB of 10 GB virtual memory used. Killing container.
>  Dump of the process-tree for container_1531909575787_0039_02_000001 :
> | - PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS) 
> SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE|
> | - 11516 11514 11516 11516 (bash) 1 3 115863552 682 /bin/bash -c 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_000001
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM 
> 1>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_000001/stdout
>  
> 2>/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_000001/stderr|
> | - 11755 11516 11516 11516 (java) 1142 71 10658242560 119576 
> /usr/lib/jvm/java-openjdk/bin/java 
> -Dlog4j.configuration=container-log4j.properties -Dlog4j.debug=true 
> -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/containers/application_1531909575787_0039/container_1531909575787_0039_02_000001
>  -Dyarn.app.container.log.filesize=1048576 -Dhadoop.root.logger=INFO,CLA 
> -Dhadoop.root.logfile=syslog -Dsubmitter.user=dev 
> org.apache.oozie.action.hadoop.LauncherAM
>  Container killed on request. Exit code is 143
>  Container exited with a non-zero exit code 143
>  For more detailed output, check the application tracking page: 
> [http://ip-10-20-201-36.us-gov-west-1.compute.internal:8088/cluster/app/application_1531909575787_0039]
>  Then click on links to logs of each attempt.
>  . Failing the application.|



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to