You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2015/05/12 08:50:59 UTC
[jira] [Comment Edited] (TEZ-2426) Ensure the eventRouter thread
completes before switching to a new task and thread safety fixes in
IPOContexts.
[ https://issues.apache.org/jira/browse/TEZ-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539369#comment-14539369 ]
Jeff Zhang edited comment on TEZ-2426 at 5/12/15 6:50 AM:
----------------------------------------------------------
[~daijy], This jira should not change that behavior, might be a regression, looking at that.
was (Author: zjffdu):
[~daijy], This jira should not change that behavior, might be a regression.
> Ensure the eventRouter thread completes before switching to a new task and thread safety fixes in IPOContexts.
> --------------------------------------------------------------------------------------------------------------
>
> Key: TEZ-2426
> URL: https://issues.apache.org/jira/browse/TEZ-2426
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Bikas Saha
> Assignee: Siddharth Seth
> Priority: Critical
> Fix For: 0.7.0
>
> Attachments: TEZ-2426.1.txt, TEZ-2426.2.txt, am.log, container.log
>
>
> Sequence of events
> 1) Task A starts in a container
> 2) Task A complete event comes to AM
> 3) Task B starts in the same container
> 4) Task A's input calls some method on its context. Crashes with NPE
> 5) The crash sends an input failed event for Task A to the AM
> 6) Task A state machine crashes saying cannot handle failed after success
> In some cases, it could be that status update event is also sent after completion, though not sure if its related to the failed event being sent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)