[
https://issues.apache.org/jira/browse/TEZ-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904694#comment-14904694
]
Hitesh Shah edited comment on TEZ-2758 at 9/23/15 3:46 PM:
-----------------------------------------------------------
bq. Right, It is not necessary to write DAGFinishedEvent to recovery file after
we write it to summary log. We won't read recovery file as long as summary log
says completed. That means the append API could be removed. Will post a patch
soon.
For the first dag finished event seen, lets write the dag finished to both
summary and recovery log but after that for any retrospective failures, only
write to summary but not to the main log ( if the outputstream has been closed
). Does that work?
was (Author: hitesh):
bq. Right, It is not necessary to write DAGFinishedEvent to recovery file after
we write it to summary log. We won't read recovery file as long as summary log
says completed. That means the append API could be removed. Will post a patch
soon.
Lets write the dag finished to both summary and recovery log but after that for
any retrospective failures, only write to summary but not to the main log ( if
the outputstream has been closed ). Does that work?
> Remove append API in RecoveryService after TEZ-1909
> ---------------------------------------------------
>
> Key: TEZ-2758
> URL: https://issues.apache.org/jira/browse/TEZ-2758
> Project: Apache Tez
> Issue Type: Improvement
> Affects Versions: 0.6.2
> Reporter: Jeff Zhang
> Assignee: Jeff Zhang
>
> After TEZ-1909, there would be no case for append recovery file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
