Mailing-List: contact dev-help@tajo.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tajo.incubator.apache.org
Date: Sun, 13 Oct 2013 14:28:43 +0000 (UTC)
From: "Hyunsik Choi (JIRA)" <jira@apache.org>
To: dev@tajo.incubator.apache.org
Message-ID: <JIRA.12673606.1381674059335.57436.1381674523247@arcas>
In-Reply-To: <JIRA.12673606.1381674059335@arcas>
References: <JIRA.12673606.1381674059335@arcas>
Subject: [jira] [Updated] (TAJO-250) QueryMaster must send the query finish
 heartbeat.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hyunsik Choi updated TAJO-250:
------------------------------

    Status: Patch Available  (was: Open)

> 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)