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

László Bodor edited comment on TEZ-4061 at 6/24/23 12:49 PM:
-------------------------------------------------------------

thanks for reporting this [~glapark], would you like to open a PR with the fix 
that you attached as  [^diff.diff] ? (assigned this jira to you, let me know if 
you don't have the bandwidth to work on this)


was (Author: abstractdog):
thanks for reporting this [~glapark], would you like to open a PR with the fix 
that you attached as  [^diff.diff] ?

> InputAttemptIdentifier and CompositeInputAttemptIdentifier cannot be compared 
> for equality
> ------------------------------------------------------------------------------------------
>
>                 Key: TEZ-4061
>                 URL: https://issues.apache.org/jira/browse/TEZ-4061
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.9.1
>            Reporter: Sungwoo Park
>            Assignee: Sungwoo Park
>            Priority: Major
>             Fix For: 0.10.3
>
>         Attachments: diff.diff
>
>
> InputFailedEvent creates InputAttemtpIdentifier. Since 
> InputAttemptIdentifier.equals() tests getClass(), comparing 
> InputAttemptIdentifier and CompositeAttemptIdentifier always returns false. 
> As a result, the obsolete event reported in InputFailedEvent never matches 
> CompositeAttemptIdentifier contained in ShuffleManager.obsoletedInputs and 
> ShuffleScheduler.obsoleteInputs.
> When the input of a Task becomes lost, this leads to many redundant reports 
> of fetch failures.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to