[jira] [Resolved] (TEZ-4338) Tez should consider node information to realize OUTPUT_LOST as early as possible - upstream(mapper) problems

["László Bodor (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TEZ-4338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

László Bodor resolved TEZ-4338.
-------------------------------
    Resolution: Fixed

> Tez should consider node information to realize OUTPUT_LOST as early as possible - upstream(mapper) problems
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: TEZ-4338
>                 URL: https://issues.apache.org/jira/browse/TEZ-4338
>             Project: Apache Tez
>          Issue Type: Improvement
>    Affects Versions: 0.10.1
>            Reporter: László Bodor
>            Assignee: László Bodor
>            Priority: Major
>             Fix For: 0.10.2
>
>          Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> Finally, I decided to split TEZ-4139 into 2 different tasks, because handling upstream problems can be fixed independently and I'm focusing on that now
> So, from TEZ-4139, this ticket is intended to handle downstream failures as:
> collect all reported upstream mapper task attempts for a vertex, and if it's beyond a certain amount for the same source(map) host, blame mapper task immediately => blame mapper task attempt as soon as possible if read error is likely because of upstream node failure (somewhat similar goal to TEZ-3910, but currently TEZ-3910 is about to give the power of failure downstream task completely to AM)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)