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

Jeff Zhang edited comment on TEZ-2581 at 11/2/15 11:41 AM:
-----------------------------------------------------------

Upload new patch. Address most of the issues in comments. [~bikassaha] Please 
help review. 
Regarding the test.
* Unit Test
** TestRecoveryParser -- test the bulding of DAGRecoveryData including test 
whether it is recoverable
** org.apache.tez.dag.app.dag.impl.TestDAGRecovery -- test the new state 
machine transition due to recovery
* System Test (org.apache.tez.test.TestRecovery)
** Use RecoveryServiceWithEventHandlingHook to control when to shutdown AM
** Use 2 examples to do system test (orderedwordcount & hashjoin). Not only 
verify the dag can finally succeeded but also verify the output


was (Author: zjffdu):


Regarding the test.
* Unit Test
** TestRecoveryParser -- test the bulding of DAGRecoveryData including test 
whether it is recoverable
** org.apache.tez.dag.app.dag.impl.TestDAGRecovery -- test the new state 
machine transition due to recovery
* System Test (org.apache.tez.test.TestRecovery)
** Use RecoveryServiceWithEventHandlingHook to control when to shutdown AM
** Use 2 examples to do system test (orderedwordcount & hashjoin). Not only 
verify the dag can finally succeeded but also verify the output

> Umbrella for Tez Recovery Redesign
> ----------------------------------
>
>                 Key: TEZ-2581
>                 URL: https://issues.apache.org/jira/browse/TEZ-2581
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Jeff Zhang
>            Assignee: Jeff Zhang
>         Attachments: TEZ-2581-WIP-1.patch, TEZ-2581-WIP-2.patch, 
> TEZ-2581-WIP-3.patch, TEZ-2581-WIP-4.patch, TEZ-2581-WIP-5.patch, 
> TEZ-2581-WIP-6.patch, TEZ-2581-WIP-7.patch, TezRecoveryRedesignProposal.pdf, 
> TezRecoveryRedesignV1.1.pdf
>
>




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

Reply via email to