Mailing-List: contact issues-help@drill.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.incubator.apache.org
Date: Fri, 29 Aug 2014 22:29:54 +0000 (UTC)
From: "Michael England (JIRA)" <jira@apache.org>
To: issues@drill.incubator.apache.org
Message-ID: <JIRA.12736756.1409045401800.6607.1409351394543@arcas>
In-Reply-To: <JIRA.12736756.1409045401800@arcas>
References: <JIRA.12736756.1409045401800@arcas>
Subject: [jira] [Comment Edited] (DRILL-1339) Apache Drill lists dead/killed
 queries as 'Running Queries' in the UI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DRILL-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14115957#comment-14115957 ] 

Michael England edited comment on DRILL-1339 at 8/29/14 10:28 PM:
------------------------------------------------------------------

[~hgunes] - It seems that issue 1326 as you posted above is the same issue so 1339 and 1326 can be merged to add the above log detail if necessary.

Mike


was (Author: mikeengland):
[~hgunes] - It seems that issue 1326 as you posted above is the same issue so these two 1339 and 1326 can be merged to add the above log detail if necessary.

Mike

> Apache Drill lists dead/killed queries as 'Running Queries' in the UI
> ---------------------------------------------------------------------
>
>                 Key: DRILL-1339
>                 URL: https://issues.apache.org/jira/browse/DRILL-1339
>             Project: Apache Drill
>          Issue Type: Bug
>    Affects Versions: 0.4.0
>         Environment: MapR v3.1
>            Reporter: Michael England
>              Labels: apache, dead, dissapearing, drill, killed, not, profile, queries, running, ui
>             Fix For: 0.6.0
>
>
> The Apache Drill UI lists queries that are dead/have been killed as 'Running Queries' on the 'Profiles' page.
> When grepping for the Query GUID of a dead query that is listed as currently running in the drill directory, I found the following outputs in a drillbit.log:
> drillbit.out:11:56:58.852 [1d1d4a6d-c6e6-4f7a-87ba-35c9cb772109:frag:0:0] ERROR o.a.h.h.z.RecoverableZooKeeper - ZooKeeper exists failed after 3 retries
> drillbit.out:11:56:58.853 [1d1d4a6d-c6e6-4f7a-87ba-35c9cb772109:frag:0:0] ERROR o.a.h.h.zookeeper.ZooKeeperWatcher - hconnection Received unexpected KeeperException, re-throwing exception
> drillbit.out:11:57:15.359 [1d1d4a6d-c6e6-4f7a-87ba-35c9cb772109:frag:0:0] ERROR o.a.h.h.z.RecoverableZooKeeper - ZooKeeper exists failed after 3 retries
> drillbit.out:11:57:15.360 [1d1d4a6d-c6e6-4f7a-87ba-35c9cb772109:frag:0:0] ERROR o.a.h.h.zookeeper.ZooKeeperWatcher - hconnection Received unexpected KeeperException, re-throwing exception
> drillbit.out:11:57:31.866 [1d1d4a6d-c6e6-4f7a-87ba-35c9cb772109:frag:0:0] ERROR o.a.h.h.z.RecoverableZooKeeper - ZooKeeper exists failed after 3 retries
> drillbit.out:11:57:31.866 [1d1d4a6d-c6e6-4f7a-87ba-35c9cb772109:frag:0:0] ERROR o.a.h.h.zookeeper.ZooKeeperWatcher - hconnection Received unexpected KeeperException, re-throwing exception
> drillbit.out:11:57:48.373 [1d1d4a6d-c6e6-4f7a-87ba-35c9cb772109:frag:0:0] ERROR o.a.h.h.z.RecoverableZooKeeper - ZooKeeper exists failed after 3 retries
> drillbit.out:11:57:48.374 [1d1d4a6d-c6e6-4f7a-87ba-35c9cb772109:frag:0:0] ERROR o.a.h.h.zookeeper.ZooKeeperWatcher - hconnection Received unexpected KeeperException, re-throwing exception
> sqlline.log:2014-08-20 11:58:12,966 [SIGINT handler] DEBUG o.a.drill.exec.client.DrillClient - Cancelling query 1d1d4a6d-c6e6-4f7a-87ba-35c9cb772109
> There needs to be some logic which moves these queries from the 'Running Queries' section to 'Failed Queries' or something to that effect.


--
This message was sent by Atlassian JIRA
(v6.2#6252)