Support Questions

Find answers, ask questions, and share your expertise
Check out our newest addition to the community, the Cloudera Data Analytics (CDA) group hub.

Container killed with Exit Code is 143, not restarting

New Contributor

My container is getting killed due to OOM. But it does not get restarted after getting killed. What configuration option is available so that the container is restarted on that node?

2019-02-15 05:36:04,623 INFO org.apache.flink.yarn.YarnResourceManager - Closing TaskExecutor connection container_1542395513696_0010_01_000008 because: Container [pid=20886,containerID=container_1542395513696_0010_01_000008] is running beyond physical memory limits. Current usage: 9.8 GB of 9.8 GB physical memory used; 13.0 GB of 48.9 GB virtual memory used. Killing container. Dump of the process-tree for container_1542395513696_0010_01_000008 :

Container killed on request. Exit code is 143 Container exited with a non-zero exit code 143


Cloudera Employee


Exit Code 143 happens due to multiple reasons and one of them is related to Memory/GC issues. Your default Mapper/reducer memory setting may not be sufficient to run the large data set. Thus, try setting up higher AM, MAP and REDUCER memory when a large yarn job is invoked. 

For more please refer to this link.




Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.