[
https://issues.apache.org/jira/browse/TAJO-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794014#comment-13794014
]
Hudson commented on TAJO-250:
-----------------------------
FAILURE: Integrated in Tajo-trunk-postcommit #510 (See
[https://builds.apache.org/job/Tajo-trunk-postcommit/510/])
TAJO-250: QueryMaster must send the query finish heartbeat. (fixed a missing
part) (hyunsik:
https://git-wip-us.apache.org/repos/asf?p=incubator-tajo.git&a=commit&h=447b50e99e7fdf7079846e6b13e38fad6e0b2c1d)
*
tajo-core/tajo-core-backend/src/main/java/org/apache/tajo/master/querymaster/QueryMaster.java
> QueryMaster must send the query finish heartbeat.
> -------------------------------------------------
>
> Key: TAJO-250
> URL: https://issues.apache.org/jira/browse/TAJO-250
> Project: Tajo
> Issue Type: Bug
> Components: master, web UI
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.2-incubating
>
> Attachments: TAJO-250_2.patch, TAJO-250.patch
>
>
> In the current implementation, QueryMaster only depends on its heartbeat
> thread for all kinds of reports. When a query master task without any
> succeeded report is moved to the finished list, the finish report may be
> omitted. As a result, QueryJobManager occasionally does not update the finish
> state (e.g., finish time and query state) for some queries even though the
> queries are already finished. This patch fixes this bug.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
