[
https://issues.apache.org/jira/browse/TEZ-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519476#comment-14519476
]
Hitesh Shah commented on TEZ-1521:
----------------------------------
Aren't events put in pending queue only on the destination vertex? Or are there
some events also now being queued on the source vertex?
For source vertex, we log events to recovery only when they are generated by
the input initializer, tasks, etc. Could you explain what you observed with the
events being logged twice? i.e. which events are pushed to the pending queue
and end up getting logged twice? It will be good to understand which kind of
events are being queued up and how we should handle them.
> VertexDataMovementEventsGeneratedEvent may be logged twice in recovery log
> ---------------------------------------------------------------------------
>
> Key: TEZ-1521
> URL: https://issues.apache.org/jira/browse/TEZ-1521
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Jeff Zhang
> Assignee: Jeff Zhang
> Priority: Critical
> Attachments: TEZ-1521-1.patch
>
>
> The TezEvents may be added to pendingTaskEvents and route again later when
> task is not scheduled. In this case, VertexDataMovementEventsGeneratedEvent
> will been logged twice.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
