You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Peter Cseh (JIRA)" <ji...@apache.org> on 2018/09/18 11:41:01 UTC
[jira] [Issue Comment Deleted] (OOZIE-3307) [core][oya] Limit heap
usage of LauncherAM
[ https://issues.apache.org/jira/browse/OOZIE-3307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Cseh updated OOZIE-3307:
------------------------------
Comment: was deleted
(was: Taking a quick look on the patch it looks like a fine improvement. +1 (pending jenkins) on it.
There are some changes in the root pom.xml which are seemingly unrelated to this issue. Maybe they are leftovers from an other patch you're working on. Please remove them before commit, but don't wait for an other Jenkins build for it.)
> [core][oya] Limit heap usage of LauncherAM
> ------------------------------------------
>
> Key: OOZIE-3307
> URL: https://issues.apache.org/jira/browse/OOZIE-3307
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: 5.0.0
> Reporter: Sabir Naikwadi
> Assignee: Andras Piros
> Priority: Critical
> Fix For: 5.1.0
>
> Attachments: OOZIE-3307.001.patch, OOZIE-3307.002.patch
>
>
> 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)