You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Dagang Wei (Jira)" <ji...@apache.org> on 2022/05/22 20:08:00 UTC

[jira] [Commented] (TEZ-3910) Single node can cause Tez job to fail during shuffle

    [ https://issues.apache.org/jira/browse/TEZ-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17540677#comment-17540677 ] 

Dagang Wei commented on TEZ-3910:
---------------------------------

What's the status of the patch? We are running into the problem, looking to backport to 0.9.2.

> Single node can cause Tez job to fail during shuffle
> ----------------------------------------------------
>
>                 Key: TEZ-3910
>                 URL: https://issues.apache.org/jira/browse/TEZ-3910
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.9.1
>            Reporter: Kuhu Shukla
>            Assignee: Kuhu Shukla
>            Priority: Major
>         Attachments: TEZ-3910.001.patch, TEZ-3910.002.patch, TEZ-3910.003.patch, TEZ-3910.004.patch, TEZ-3910.005.patch
>
>
> There is a race where a downstream task that is running into fetch failures due to bad output from the upstream task can continue to blame itself for the failure before the AM can do a re-run of the upstream offending task and fix the fetch failure. This causes the DAG to fail even if a single node fails.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)