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 2015/12/13 02:12:46 UTC

[jira] [Commented] (TEZ-2996) TestAnalyzer fails in trunk

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

Bikas Saha commented on TEZ-2996:
---------------------------------

Related to the recovery refactoring. [~zjffdu] Please review. termination cause and diagnostics were not set before writing the unsuccessful completion event. So the analyzer was not generating the expected critical path.
Also, could you please link this and the other recovery related bugs (history parser test failure) to the main recovery jira or make them sub-tasks of the recovery jira. This was we will not forget to backport all the of them.

Separate question - upon recovery - will members like diagnostics/termination cause be refreshed from recovered state or not?

In task attempt imp there is the following TODO - is it valid or can be removed?
{code}      // TODO Creating the remote task here may not be required in case of
      // recovery.{code}

> TestAnalyzer fails in trunk
> ---------------------------
>
>                 Key: TEZ-2996
>                 URL: https://issues.apache.org/jira/browse/TEZ-2996
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>         Attachments: TEZ-2996.1.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)