Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Almost all our entities (Vertex, Task etc) are state machine based and written using a formal state machine. But DAGAppMaster is not written on a formal state machine even though it has a state machine based behavior. This jira is for refactoring it into state machine based
Attachments
Attachments
Issue Links
- relates to
-
TEZ-1954 Multiple instances of Inconsistent synchronization in org.apache.tez.dag.app.DAGAppMaster.
- Open
-
TEZ-1843 AM should go to KILLED state when it is killed in RUNNING state
- Open
-
TEZ-1885 Should check whether AM is shutting down first in submitDAGToAppMaster
- Open
-
TEZ-2375 Don't return dag status to client when dag is still in recovering
- Open
-
TEZ-2428 Investigate ignored event: DAGAppMaster: ignore event when DAGAppMaster is in the state of STOPPED, eventType=NEW_DAG_SUBMITTED
- Open
-
TEZ-2359 Deadlock in DAGAppMaster
- Resolved
-
TEZ-2307 Possible wrong error message when submitting new dag
- Closed