[TEZ-3198] Shuffle failures for the trailing task in a vertex are often fatal to the entire DAG

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 0.7.0, 0.8.2
• Target Version/s: 0.7.1
• Assignee: Unassigned
• Reporter: Jason Darrell Lowe
• Created: 05/Apr/16 19:20
• Updated: 20/Sep/18 14:42
• Resolved: 20/Sep/18 14:19

Description

I've seen an increasing number of cases where a single-node failure caused the whole Tez DAG to fail. These scenarios are common in that they involve the last task of a vertex attempting to complete a shuffle where all the peer tasks have already finished shuffling. The last task's attempt encounters errors shuffling one of its inputs and keeps reporting it to the AM. Eventually the attempt decides it must be the cause of the shuffle error and fails. The subsequent attempts all do the same thing, and eventually we hit the task max attempts limit and fail the vertex and DAG.

Issue Links

• duplicates: TEZ-3972 Tez DAG can hang when a single task fails to fetch