You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2013/06/14 19:28:20 UTC

[jira] [Resolved] (TEZ-207) DAGClient should fall back to the RM to get state if the AM goes away

     [ https://issues.apache.org/jira/browse/TEZ-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bikas Saha resolved TEZ-207.
----------------------------

       Resolution: Fixed
    Fix Version/s: 0.2.0
         Assignee: Bikas Saha

The following commit fixed this.
commit f6554fe8da0f7d01df464f739770f57e4407677b
Author: Bikas Saha <bi...@apache.org>
Date:   Thu Jun 13 14:29:19 2013 -0700

    TEZ-211. TezClient.submit should return a DAGClient instead of an AppId (bikas)
                
> DAGClient should fall back to the RM to get state if the AM goes away
> ---------------------------------------------------------------------
>
>                 Key: TEZ-207
>                 URL: https://issues.apache.org/jira/browse/TEZ-207
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Siddharth Seth
>            Assignee: Bikas Saha
>            Priority: Critical
>              Labels: TEZ-0.2.0
>             Fix For: 0.2.0
>
>
> Opposite of TEZ-160.
> If the DAG AM goes away (job completes), there's no way to fetch status information other than talking directly to the RM. The DAG client should take care of this.
> This gets complicated in the case where multiple DAGs per AM - in case the AM goes away. That's likely a problem for later when multiple dags exist per AM - and will likely be solved once Tez has some kind of history information (directly or via YARN). 
> For now, DAGClient should fall back to the RM.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira