From user-return-2082-apmail-drill-user-archive=drill.apache.org@drill.apache.org Tue May 5 07:55:04 2015 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 5148E17F2B for ; Tue, 5 May 2015 07:55:04 +0000 (UTC) Received: (qmail 8869 invoked by uid 500); 5 May 2015 07:55:04 -0000 Delivered-To: apmail-drill-user-archive@drill.apache.org Received: (qmail 8806 invoked by uid 500); 5 May 2015 07:55:04 -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 8793 invoked by uid 99); 5 May 2015 07:55:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 May 2015 07:55:03 +0000 X-ASF-Spam-Status: No, hits=2.4 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: message received from 54.191.145.13 which is an MX secondary for user@drill.apache.org) Received: from [54.191.145.13] (HELO mx1-us-west.apache.org) (54.191.145.13) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 May 2015 07:54:57 +0000 Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 01E3524C9E for ; Tue, 5 May 2015 07:54:36 +0000 (UTC) Received: by obcux3 with SMTP id ux3so127234953obc.2 for ; Tue, 05 May 2015 00:54:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=A7Ne4PPB9j8W17nJMhQiTV+canB4PEp9Ziwpr/zbpcc=; b=WYK7HzpWo3jjD3f67lg4CCcN75v3cB6XQxjloqJqZEKGCFUke/W4jzMKfnGRY7gD03 tfu0XV3zTbyLvIYriDPFXgyrWaoXZyLLLlqpoKB/vved+iRGZwUlpcb54KJ8NHzBX465 Cv/Ia197sMjKkHpf3Gi1S6NpyMd5ScpJuhFQWwJpJEuwljpXQ3Wa4W+/84knxnWyjuPf nPm0sOrtywP/6ZlUYet96rCV1VEhQAqwCxvDmZ2yemb452YGAc85jx37etwmD1K9fOKe s4FzH32id4chTcrSiMeFC89KoYK10oK699jazEXfzl7JNlzR1jqoBK7DlQ9Q07RxetOW j9LA== MIME-Version: 1.0 X-Received: by 10.182.130.201 with SMTP id og9mr21459027obb.60.1430812473657; Tue, 05 May 2015 00:54:33 -0700 (PDT) Received: by 10.76.27.231 with HTTP; Tue, 5 May 2015 00:54:33 -0700 (PDT) Date: Tue, 5 May 2015 15:54:33 +0800 Message-ID: Subject: How to deploy Drill to achieve optimal performance From: George Lu To: user@drill.apache.org Content-Type: multipart/alternative; boundary=089e01175e0b3b910a051550fd99 X-Virus-Checked: Checked by ClamAV on apache.org --089e01175e0b3b910a051550fd99 Content-Type: text/plain; charset=UTF-8 Hi all, These days, I am trying Drill to see whether Drill fits the realtime/near realtime interactive queries requirement. I have a HBase server, underlying HDFS contains three data nodes, and I deployed 7 Drill nodes within the cluster. I have several million records in the HBase table and I issue queries like SUM, MAX, COUNT against the table and found the Drill costs like 5 to 6 minutes on average to get the result. Such latency is not ideal for interactive use. I know Drill is used for low-latency query, so I would like to ask for help how to achieve that? How to make Drill run queries in low-latency (in seconds not minutes)? Any suggestions are welcome! Thanks! George --089e01175e0b3b910a051550fd99--