From issues-return-48474-archive-asf-public=cust-asf.ponee.io@drill.apache.org Fri Jan 5 22:30:14 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 5BF10180647 for ; Fri, 5 Jan 2018 22:30:14 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 4B83B160C27; Fri, 5 Jan 2018 21:30:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 915BD160C15 for ; Fri, 5 Jan 2018 22:30:13 +0100 (CET) Received: (qmail 652 invoked by uid 500); 5 Jan 2018 21:30:12 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 642 invoked by uid 99); 5 Jan 2018 21:30:12 -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, 05 Jan 2018 21:30:12 +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 47CEF1A02A6 for ; Fri, 5 Jan 2018 21:30:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.911 X-Spam-Level: X-Spam-Status: No, score=-99.911 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-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 EpMt8BdQ0-w3 for ; Fri, 5 Jan 2018 21:30:11 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 8FB375FAD6 for ; Fri, 5 Jan 2018 21:30:10 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 793F4E00B4 for ; Fri, 5 Jan 2018 21:30:07 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id AC4F2212F7 for ; Fri, 5 Jan 2018 21:30:00 +0000 (UTC) Date: Fri, 5 Jan 2018 21:30:00 +0000 (UTC) From: "Pritesh Maker (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DRILL-6061) Feature Request: Global Query List showing queries from all Drill foreman nodes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DRILL-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313923#comment-16313923 ] Pritesh Maker commented on DRILL-6061: -------------------------------------- Does configurign the persistent store for Drill to zookeeper address this requirement? https://drill.apache.org/docs/persistent-configuration-storage/ > Feature Request: Global Query List showing queries from all Drill foreman nodes > ------------------------------------------------------------------------------- > > Key: DRILL-6061 > URL: https://issues.apache.org/jira/browse/DRILL-6061 > Project: Apache Drill > Issue Type: New Feature > Components: Server, Documentation, Metadata, Query Planning & Optimization, Tools, Build & Test, Web Server > Affects Versions: 1.11.0 > Environment: MapR 5.2 > Reporter: Hari Sekhon > > Feature Request to add a Global Query List to show all queries executed across all Drill nodes in a cluster for better management and auditing. > Right now there doesn't appear to be a way to see all queries across all nodes in a Drill cluster. The Web UI on any given Drill node only shows the queries coordinated by that local node if acting as the foreman for the query, so if using ZooKeeper or a Load Balancer to distribute queries via different Drill nodes then the query list will be spread across lots of different nodes with no global timeline of queries. > This seems to leave a bit of a gap in auditing functionality, with the only other option that I can think of being immediately available is to limit all query submissions via a single foreman node so the query list is complete on that node - although that doesn't seem like a great idea in terms of load distribution of query planning, coordination and final aggregation steps. I've made load balancing configurations for Apache Drill and similar technologies that could be used for that purpose with failover support to maintain high availability at https://github.com/HariSekhon/nagios-plugins/tree/master/haproxy) but would still prefer if Drill was designed to store the global list of queries submitted in a centralized place. -- This message was sent by Atlassian JIRA (v6.4.14#64029)