[ 
https://issues.apache.org/jira/browse/TAJO-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hyunsik Choi updated TAJO-1113:
-------------------------------
    Description: 
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.

  was:
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.


> SubQuery in KILLED state should handle some ignorable event.
> ------------------------------------------------------------
>
>                 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: Minor
>             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)

Reply via email to