You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2014/07/10 16:34:04 UTC

[jira] [Commented] (TEZ-1273) Refactor DAGAppMaster to state machine based

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

Jeff Zhang commented on TEZ-1273:
---------------------------------

Attach the state machine diagram.

For a non-session case, the normal flow would be NEW->INITED->RUNNING->SUCCEED/FAILED/KILLED/ERROR->TERMINATED
For a session case, the flow would be NEW->[ INITED->IDLE->RUNNING ] ...

> Refactor DAGAppMaster to state machine based
> --------------------------------------------
>
>                 Key: TEZ-1273
>                 URL: https://issues.apache.org/jira/browse/TEZ-1273
>             Project: Apache Tez
>          Issue Type: Improvement
>    Affects Versions: 0.4.0
>            Reporter: Jeff Zhang
>            Assignee: Jeff Zhang
>         Attachments: dag_app_master.pdf
>
>
> 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



--
This message was sent by Atlassian JIRA
(v6.2#6252)