You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Parth Chandra (JIRA)" <ji...@apache.org> on 2015/04/20 20:03:58 UTC
[jira] [Updated] (DRILL-1339) Apache Drill lists dead/killed
queries as 'Running Queries' in the UI
[ https://issues.apache.org/jira/browse/DRILL-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Parth Chandra updated DRILL-1339:
---------------------------------
Component/s: Client - HTTP
> 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
> Components: Client - HTTP
> Affects Versions: 0.4.0
> Environment: MapR v3.1
> Reporter: Michael England
> Assignee: Jinfeng Ni
> Priority: Blocker
> Labels: apache, dead, dissapearing, drill, killed, not, profile, queries, running, ui
> Fix For: 0.7.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.3.4#6332)