We recently launched an EMR cluster with latest version of Oozie that is Oozie 5.0.0.
We understand the Oozie launcher is no more a mpareduce job in Yarn. We see that it shows up as 'Oozie launcher' in the Yarn UI. Our workflow has a Spark and a Sqoop job, and the launcher is failing first attempt with running out of memory error, causing it to try multiple attempts. Please advise where we can set the memory limits for Oozie launcher, in order to work around this error? AM Container for appattempt_1534385557019_0066_000001 exited with exitCode: -104 Failing this attempt.Diagnostics: Container [pid=19109,containerID=container_1534385557019_0066_01_000001] is running beyond physical memory limits. Current usage: 2.2 GB of 2 GB physical memory used; 9.9 GB of 10 GB virtual memory used. Killing container. Thank you Suresh.
