[
https://issues.apache.org/jira/browse/TEZ-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492784#comment-14492784
]
Hitesh Shah commented on TEZ-2303:
----------------------------------
[~zjffdu] A couple of things - not sure if the write lock is sufficient:
- should we disable the dag client service until all the recovery data is
read completely and the recover event is sent to the dag?
- next, even after we send the recover event to dag, the recovery process is
asynchronous so a client can query dag status so do we need to build in any
additional checks to guard against getStatus/getProgress while the recovered
data is being re-built?
> ConcurrentModificationException while processing recovery
> ---------------------------------------------------------
>
> Key: TEZ-2303
> URL: https://issues.apache.org/jira/browse/TEZ-2303
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.6.0
> Reporter: Jason Lowe
> Assignee: Jeff Zhang
>
> Saw a Tez AM log a few ConcurrentModificationException messages while trying
> to recover from a previous attempt that crashed. Exception details to follow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
