[
https://issues.apache.org/jira/browse/TAJO-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172205#comment-14172205
]
Hudson commented on TAJO-1113:
------------------------------
SUCCESS: Integrated in Tajo-block_iteration-branch-build #15 (See
[https://builds.apache.org/job/Tajo-block_iteration-branch-build/15/])
TAJO-1113: SubQuery in KILLED state should handle unexpected events. (hyunsik:
rev 3d334f3f45443b4d39a4d029de2482e5629a6e10)
* tajo-core/src/main/java/org/apache/tajo/master/querymaster/SubQuery.java
* CHANGES
> SubQuery in KILLED state should handle unexpected events.
> ---------------------------------------------------------
>
> Key: TAJO-1113
> URL: https://issues.apache.org/jira/browse/TAJO-1113
> Project: Tajo
> Issue Type: Bug
> Components: query master
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Priority: Blocker
> Fix For: 0.9.0
>
>
> Currently, {{KILLED}} state in SubQuery does not handle any event. As I
> mentioned in TAJO-1111, {{QueryUnit}} in even terminal states may receive
> additional unexpected events from a running tasks because a running task
> reporter sends a progress periodically; that is the report is not
> synchronized with a task life cycle. As a result, When a killed {{QueryUnit}}
> receives unexpected events, it can cause some event towards {{SubQuery}}.
> But, {{SubQuery}} does not handle any addition events if {{SubQuery}} is
> already in {{KILLED}}.
> This patch adds some transitions to SubQuery in order to fix the above
> problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
