[
https://issues.apache.org/jira/browse/TEZ-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513894#comment-14513894
]
Jeff Zhang commented on TEZ-2303:
---------------------------------
[~hitesh] I didn't find way to stop accepting connections from client after DAG
is recovered. Upload a another patch to use a different way.
* Register to RM after recovery is done so that client will get the host/port
after the recovery is completed.
* There may be still one potential issue that if recovery fails, it would
unregister to RM without register first, not sure whether this would cause any
YarnException.
> 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
> Attachments: TEZ-2303-1.patch, TEZ-2303-2.patch, TEZ-2303-4.patch
>
>
> 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)
