[
https://issues.apache.org/jira/browse/TEZ-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14903577#comment-14903577
]
Hitesh Shah edited comment on TEZ-2758 at 9/22/15 11:27 PM:
------------------------------------------------------------
[~zjffdu] The option to close on a new dag submission seems interesting. Only
consideration would be whether a dag finished event for an older dag can show
up after a new dag is submitted? Also, my original question was whether we read
the main dag file even if summary log says completed? Assuming we do not read
dag data if there is another dag in the summary then we can first close all
existing open streams when the new dag is submitted and also drop all older dag
events that show up after the stream has been closed?
was (Author: hitesh):
[~zjffdu] The option to close on a new dag submission seems interesting. Only
consideration would be whether a dag finished event for an older dag can show
up after a dag submitted? Also, my original question was whether we read the
main dag file even if summary log says completed? Assuming we do not read dag
data if there is another dag in the summary then we can first close stream when
new dag is submitted and also drop all older dag events that show up after the
stream has been closed?
> 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)
