Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E902F200C6B for ; Tue, 28 Mar 2017 08:15:50 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E7CFC160B99; Tue, 28 Mar 2017 06:15:50 +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 466AD160B85 for ; Tue, 28 Mar 2017 08:15:50 +0200 (CEST) Received: (qmail 77918 invoked by uid 500); 28 Mar 2017 06:15:49 -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 77909 invoked by uid 99); 28 Mar 2017 06:15:49 -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; Tue, 28 Mar 2017 06:15:49 +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 1D9DE1A008E for ; Tue, 28 Mar 2017 06:15:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id mK1_-UgJvrkd for ; Tue, 28 Mar 2017 06:15:48 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 320275FACC for ; Tue, 28 Mar 2017 06:15:48 +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 AB77DE002F for ; Tue, 28 Mar 2017 06:15:47 +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 AC3B825CE2 for ; Tue, 28 Mar 2017 06:15:41 +0000 (UTC) Date: Tue, 28 Mar 2017 06:15:41 +0000 (UTC) From: "Kunal Khatua (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (DRILL-5287) Provide option to skip updates of ephemeral state changes in Zookeeper MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 28 Mar 2017 06:15:51 -0000 [ https://issues.apache.org/jira/browse/DRILL-5287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kunal Khatua closed DRILL-5287. ------------------------------- Verified by running a SQLLine session with the update disabled and running a sufficiently long running query. The web-UI does not list the query in running state, but only when the query is complete and the web-page refreshed. > Provide option to skip updates of ephemeral state changes in Zookeeper > ---------------------------------------------------------------------- > > Key: DRILL-5287 > URL: https://issues.apache.org/jira/browse/DRILL-5287 > Project: Apache Drill > Issue Type: Bug > Affects Versions: 1.9.0 > Reporter: Padma Penumarthy > Assignee: Padma Penumarthy > Labels: doc-impacting, ready-to-commit > Fix For: 1.10.0 > > > We put transient profiles in zookeeper and update state as query progresses and changes states. It is observed that this adds latency of ~45msec for each update in the query execution path. This gets even worse when high number of concurrent queries are in progress. For concurrency=100, the average query response time even for short queries is 8 sec vs 0.2 sec with these updates disabled. For short lived queries in a high-throughput scenario, it is of no value to update state changes in zookeeper. We need an option to disable these updates for short running operational queries. -- This message was sent by Atlassian JIRA (v6.3.15#6346)