Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.0.4-alpha
-
None
-
None
Description
When a job runs in Uber-AM mode the JVM settings (e.g.: heap sizing), container sizing, and environment variables are not propagated to the AM. This means running in uber-AM mode is not as simple as enabling mapreduce.job.ubertask.enable since lack of proper heap/container settings can doom the AM to crash or lack of proper environment variables can prevent the task code from properly running.
Attachments
Issue Links
- is related to
-
OOZIE-1372 When using uber mode, Oozie should also make the AM container size larger
- Closed