[TEZ-1323] Insufficent diagnostics on console when dag fails due to an exception in a task

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Duplicate
• Assignee: Unassigned
• Reporter: Hitesh Shah
• Created: 28/Jul/14 21:04
• Updated: 14/Oct/14 16:25
• Resolved: 14/Oct/14 16:25

Description

For TEZ-1322, the following diagnostic was generated:

14/07/28 13:26:29:157 INFO examples.OrderedWordCount: DAG 1 diagnostics: [Vertex failed, vertexName=initialmap, vertexId=vertex_1406579076951_0001_1_00, diagnostics=[Task failed, taskId=task_1406579076951_0001_1_00_000000, diagnostics=[TaskAttempt 0 failed, info=[Error: Failure while running task], TaskAttempt 1 failed, info=[Error: Failure while running task], TaskAttempt 2 failed, info=[Error: Failure while running task], TaskAttempt 3 failed, info=[Error: Failure while running task]], Vertex failed as one or more tasks failed. failedTasks:1], Vertex killed, vertexName=intermediate_reducer, vertexId=vertex_1406579076951_0001_1_01, diagnostics=[Vertex received Kill while in RUNNING state., Vertex killed as other vertex failed. failedTasks:0], Vertex killed, vertexName=finalreduce, vertexId=vertex_1406579076951_0001_1_02, diagnostics=[Vertex received Kill while in RUNNING state., Vertex killed as other vertex failed. failedTasks:0], DAG failed due to vertex failure. failedVertices:1 killedVertices:2]

Issue Links

• is duplicated by: TEZ-1238 Display more clear diagnostics info on client side on task failures