Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Container killed by ApplicationMaster. Container Killed on Request. Exit Code is 143.

Highlighted

Container killed by ApplicationMaster. Container Killed on Request. Exit Code is 143.

New Contributor

Whenever I run mapreduce program on large Data gives above error. There is no issue in program it execute successfully on small data. refer following 2 images

71495-code-143-2.png

71496-code-143.png

Thank you in advance

71494-code-143-2.png

3 REPLIES 3

Re: Container killed by ApplicationMaster. Container Killed on Request. Exit Code is 143.

New Contributor

Can you check NM logs for this container. This is probably OOM or Unix kill sig due to system level restriction on resources

Re: Container killed by ApplicationMaster. Container Killed on Request. Exit Code is 143.

New Contributor

NM logs show same error as container killed by ApplicationMaster. Container Killed on Request. Exit Code 143.

tried increasing reducer memory to 4096 mb in mapred-site.xml but still not working.

Re: Container killed by ApplicationMaster. Container Killed on Request. Exit Code is 143.

Super Collaborator

The job is timing out (after 10 minutes), it looks like your job doesn't report any progress within this timeout, causing yarn to kill the container.
You will have to figure out what your job is doing while it is killed (timeout occurs). You need to check the application logs, i.e. with this command: yarn logs -applicationId <application ID> <options>

Don't have an account?
Coming from Hortonworks? Activate your account here