[
https://issues.apache.org/jira/browse/TEZ-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17103694#comment-17103694
]
Syed Shameerur Rahman commented on TEZ-4173:
--------------------------------------------
[~abstractdog]
Yes looks like a corner case, We can safely skip vertex initialization if tasks
on that vertex started or setVertexParallelism is true (since it is called only
once during vertex life cycle and it makes sure that the no. of tasks for that
vertex are defined and won't change later).
In TEZ-4173.01.patch instead of looking at numTask we should look for
recoveryData.getVertexConfigurationDoneEvent().isSetParallelismCalled() and it
requires modification of some tests added in TEZ-4140.
> TestRecovery flaky timeout on master
> ------------------------------------
>
> Key: TEZ-4173
> URL: https://issues.apache.org/jira/browse/TEZ-4173
> Project: Apache Tez
> Issue Type: Bug
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
> Attachments: TEZ-4173.01.patch, TEZ-4173.reproduction.patch,
> am.jstack.log, surefire.jstack.log, tez4173.tar.gz
>
>
> application logs and junit output in [^tez4173.tar.gz]
> one of the running AM's jstack is [^am.jstack.log]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
