[
https://issues.apache.org/jira/browse/TEZ-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Zhang updated TEZ-2250:
----------------------------
Description:
Currently, invalid state machine transition will trigger the internal error.
Here's current logics
* Invalid transition in Task/TaskAttempt will send DAGEvent with type of
INTERNAL_ERORR to dag, and dag will trigger its InternalErrorTransition
* Invalid transition in Vertex will finish
* Invalid transition in DAG will cause it to kill all the vertices.
2 issues:
* Invalid transition in DAG/Vertex/Task/TaskAttempt are consistent, I think any
invalid transition should send DAGEvent with type of INTERNAL_ERROR and then
trigger it to kill vertices/task/task attempts
* Currently DAG/Vertex move to ERROR without wait ing for vertices/task to
complete. It would cause the aborting conflict with the running task attempt.
> Consolidate the Internal Error transition for DAG/Verex/Task/TaskAttempt
> ------------------------------------------------------------------------
>
> Key: TEZ-2250
> URL: https://issues.apache.org/jira/browse/TEZ-2250
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Jeff Zhang
>
> Currently, invalid state machine transition will trigger the internal error.
> Here's current logics
> * Invalid transition in Task/TaskAttempt will send DAGEvent with type of
> INTERNAL_ERORR to dag, and dag will trigger its InternalErrorTransition
> * Invalid transition in Vertex will finish
> * Invalid transition in DAG will cause it to kill all the vertices.
> 2 issues:
> * Invalid transition in DAG/Vertex/Task/TaskAttempt are consistent, I think
> any invalid transition should send DAGEvent with type of INTERNAL_ERROR and
> then trigger it to kill vertices/task/task attempts
> * Currently DAG/Vertex move to ERROR without wait ing for vertices/task to
> complete. It would cause the aborting conflict with the running task attempt.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
