Description
TEZ-2325 route TASK_ATTEMPT_COMPLETED_EVENT directly to the attempt, but it would cause recovery issue. Recovery need that DataMovement event is handled before TaskAttemptCompletedEvent, otherwise DataMovement event may be lost in recovering and cause the its dependent tasks hang.
2 Ways to fix this issue.
1. Still route TaskAtttemptCompletedEvent in Vertex
2. route DataMovementEvent before TaskAttemptCompeltedEvent in TezTaskAttemptListener
Attachments
Attachments
Issue Links
- breaks
-
TEZ-2418 TASK_ATTEMPT_FAILED_EVENT and TASK_COMPLETED_EVENT should move back to direct routing to attempt
- Resolved
- duplicates
-
TEZ-2402 Handle DataMovementEvent before its TaskAttemptCompletedEvent
- Resolved
-
TEZ-2403 Handle DataMovementEvent before its TaskAttemptCompletedEvent
- Resolved
- is related to
-
TEZ-1897 Create a concurrent version of AsyncDispatcher
- Closed