Reply
New Contributor
Posts: 1
Registered: ‎05-04-2018

Re: Map jobs are failing with exit code 143

I am facing the same issue, can anyone help?

 

3,372 INFO [IPC Server handler 3 on 40059] org.apache.hadoop.mapred.TaskAttemptListenerImpl: Progress of TaskAttempt attempt_1524609026181_296457_m_000156_0 is : 0.066741236
2018-05-04 07:43:33,434 INFO [IPC Server handler 9 on 40059] org.apache.hadoop.mapred.TaskAttemptListenerImpl: Progress of TaskAttempt attempt_1524609026181_296457_m_000033_0 is : 0.036332265
2018-05-04 07:43:33,451 INFO [IPC Server handler 1 on 40059] org.apache.hadoop.mapred.TaskAttemptListenerImpl: Progress of TaskAttempt attempt_1524609026181_296457_m_000422_0 is : 0.36007702
2018-05-04 07:43:33,454 INFO [IPC Server handler 5 on 40059] org.apache.hadoop.mapred.TaskAttemptListenerImpl: Progress of TaskAttempt attempt_1524609026181_296457_m_000000_0 is : 0.01545117
2018-05-04 07:43:33,555 INFO [RMCommunicator Allocator] org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Before Scheduling: PendingReds:0 ScheduledMaps:551 ScheduledReds:0 AssignedMaps:140 AssignedReds:0 CompletedMaps:4 CompletedReds:0 ContAlloc:175 ContRel:0 HostLocal:66 RackLocal:109
2018-05-04 07:43:33,557 INFO [RMCommunicator Allocator] org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Received completed container container_e68_1524609026181_296457_01_000006
2018-05-04 07:43:33,557 INFO [RMCommunicator Allocator] org.apache.hadoop.mapreduce.v2.app.rm.RMContainerAllocator: Got allocated containers 1
2018-05-04 07:43:33,557 INFO [AsyncDispatcher event handler] org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl: Diagnostics report from attempt_1524609026181_296457_m_000582_0: Container killed by the ApplicationMaster.
Container killed on request. Exit code is 143
Container exited with a non-zero exit code 143
Highlighted
Posts: 851
Topics: 1
Kudos: 197
Solutions: 105
Registered: ‎04-22-2014

Re: Map jobs are failing with exit code 143

@Haddop,

 

I moved this post to the Community that works with YARN and MR.

 

In order to see why the failures are occurring, I suggest looking at the container logs since you can see the log message shows it was killed by the application master:

Container killed by the ApplicationMaster

 

Announcements