From user-return-6719-apmail-drill-user-archive=drill.apache.org@drill.apache.org Fri Aug 19 13:10:54 2016 Return-Path: X-Original-To: apmail-drill-user-archive@www.apache.org Delivered-To: apmail-drill-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 564D919459 for ; Fri, 19 Aug 2016 13:10:54 +0000 (UTC) Received: (qmail 42201 invoked by uid 500); 19 Aug 2016 13:10:54 -0000 Delivered-To: apmail-drill-user-archive@drill.apache.org Received: (qmail 42139 invoked by uid 500); 19 Aug 2016 13:10:54 -0000 Mailing-List: contact user-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@drill.apache.org Delivered-To: mailing list user@drill.apache.org Received: (qmail 42121 invoked by uid 99); 19 Aug 2016 13:10:53 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Aug 2016 13:10:53 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 439D71A02F0 for ; Fri, 19 Aug 2016 13:10:53 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=maprtech.com Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Rmtoxurc55Ej for ; Fri, 19 Aug 2016 13:10:49 +0000 (UTC) Received: from mail-ua0-f180.google.com (mail-ua0-f180.google.com [209.85.217.180]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id C8EC05FAF4 for ; Fri, 19 Aug 2016 13:10:48 +0000 (UTC) Received: by mail-ua0-f180.google.com with SMTP id 74so78918372uau.0 for ; Fri, 19 Aug 2016 06:10:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=maprtech.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=2QcETF63AV0q+MwStKXH9h2psgve6kT9b+A/XyIkg/Y=; b=CM+YT6PooVTevKkBb79pbIse8B5ZDMM6NHxD2Yg2WpvOrPPEgZmnRECMJDZbWWO86w JGG7NEkOchpbriVn4UMIUPo5wTGhNc1/HzJB2+FhWSF3LA4+SeW4CdHvkZTJCehfKXZn spplgZIBiwTcXSuKN+2uQEvPaTUeg7186OdjM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=2QcETF63AV0q+MwStKXH9h2psgve6kT9b+A/XyIkg/Y=; b=giisqnl9N0fyWRzJZK0vmXRVEHswXPgVzRKETM3S8F0Em50DYO2vAwzfDoZEk0EL+M vxkqXOZomzJh5Gdi4yncORe5Qlvo/TGb4ZRMZ6ju5Hm6Lbh7cYamRLRdReQbgohWaFlu BnS0l2OX9SMjIyTO7UCfQSjoP+oMnnORS6jAM7wl0W4eRnctSFrbWv66wmNBEkYFwxQm N3as77YDMMnHrOc1mG+nfpS/xBgVzVKEtDxnZvTBwueDSWVzHse5it9Q2pdASQBoSFTX nff2tPqz/kB5Fg5WTbSVEFNiIO/k2/y9V9TNlBvRfdkZdpAHE28lx3qxlNHAQ0K4yjZc LSbg== X-Gm-Message-State: AEkoousPNoNMo8N+9FzXRi0phv7D0pDBNxjGbucEMh8ucuIwsGMsSyZwhQtpetKUGtKpFh7j1qXSEvApnhW4VxC/ X-Received: by 10.31.120.135 with SMTP id t129mr3859535vkc.128.1471612247472; Fri, 19 Aug 2016 06:10:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.69.81 with HTTP; Fri, 19 Aug 2016 06:10:46 -0700 (PDT) In-Reply-To: References: <7CA37304-9D69-4921-8F12-C55C599AAD8F@maprtech.com> From: Khurram Faraaz Date: Fri, 19 Aug 2016 18:40:46 +0530 Message-ID: Subject: Re: Fetch queries status from drill prompt To: user@drill.apache.org Content-Type: multipart/alternative; boundary=94eb2c03ba68421be0053a6c6df3 --94eb2c03ba68421be0053a6c6df3 Content-Type: text/plain; charset=UTF-8 There is an open JIRA DRILL-4258 Once that is fixed/implemented you can query from sys.queries or sys.statements to know about all SQL statements that are in different states. Khurram On Fri, Aug 19, 2016 at 4:45 PM, Anup Tiwari wrote: > Thanks for above info.. i found running queries information in Zookeeper > logs but i guess it is in binary or some other form. > Is their any way to read it in drill? > > Regards, > *Anup Tiwari* > Software Engineer(BI-Team),PlayGames24x7 Pvt Ltd > > On Thu, Aug 18, 2016 at 11:59 PM, Sudheesh Katkam > wrote: > > > Profiles of running queries are stored in Zookeeper (or the configured > > transient store). > > > > Thank you, > > Sudheesh > > > > > On Aug 18, 2016, at 11:23 AM, Anup Tiwari > > wrote: > > > > > > Thanks chun for info.. > > > > > > But can you tell me from where, running queries status come on profile > > > user-interface(UI)? Because if it's coming on profile UI then it must > > have > > > some back end file or something like that.. > > > On 18-Aug-2016 11:37 PM, "Chun Chang" wrote: > > > > > > Anup, > > > > > > I believe only when a query is in a "terminal", i.e. > > > cancelled/completed/failed state, then it is written to the > > > drillbit_queries.json file on the foreman node. If what you want to do > is > > > monitoring queries running on your cluster, your best bet is to > configure > > > your cluster to store profile information on HDFS and monitor through > > query > > > profile. Remember if you have a cluster, you will have a > > > drillbit_queries.json file on very cluster node where drillbit is > > running. > > > And each file only contains completed queries that were run on that > node > > as > > > foreman. You would have to aggregate to get the whole picture of your > > > cluster. Even that, you will not see running queries. > > > > > > Hope this helps. > > > > > > On Thu, Aug 18, 2016 at 12:34 AM, Anup Tiwari < > anup.tiwari@games24x7.com > > > > > > wrote: > > > > > >> Hi All, > > >> > > >> We want to see all types of queries which ran on drill cluster or > > > currently > > >> running from drill prompt, Can someone help us on this? > > >> > > >> To achieve above , we read the drill documentation and set up a > storage > > >> plugin to access local file system and able to query > > >> *"drillbit_queries.json"* log file, but in above file we are getting > > > status > > >> of all queries whose status is either "cancelled","completed" or > > "failed" > > >> but missing "running". At the same time we check drill profile > interface > > >> where we can see running queries. > > >> > > >> I am sure if we can see on User-Interface then it must be coming from > > >> somewhere. > > >> > > >> Kindly help me on this. > > >> > > >> Regards, > > >> *Anup Tiwari* > > >> Software Engineer(BI-Team),PlayGames24x7 Pvt Ltd > > >> > > > > > --94eb2c03ba68421be0053a6c6df3--