Return-Path: X-Original-To: apmail-drill-dev-archive@www.apache.org Delivered-To: apmail-drill-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C1B6D181C1 for ; Fri, 6 Nov 2015 18:43:04 +0000 (UTC) Received: (qmail 39585 invoked by uid 500); 6 Nov 2015 18:43:04 -0000 Delivered-To: apmail-drill-dev-archive@drill.apache.org Received: (qmail 39528 invoked by uid 500); 6 Nov 2015 18:43:04 -0000 Mailing-List: contact dev-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 dev@drill.apache.org Received: (qmail 39515 invoked by uid 99); 6 Nov 2015 18:43:04 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Nov 2015 18:43:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id B0483180E13 for ; Fri, 6 Nov 2015 18:43:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.898 X-Spam-Level: ** X-Spam-Status: No, score=2.898 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=maprtech.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id k1uuD9lyJmIT for ; Fri, 6 Nov 2015 18:43:03 +0000 (UTC) Received: from mail-yk0-f172.google.com (mail-yk0-f172.google.com [209.85.160.172]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id CC8D242B32 for ; Fri, 6 Nov 2015 18:43:02 +0000 (UTC) Received: by ykdr3 with SMTP id r3so193440319ykd.1 for ; Fri, 06 Nov 2015 10:43:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=maprtech.com; s=google; h=mime-version:date:message-id:subject:from:to:content-type; bh=BSkhZZQ6IIqtFNbk5YmTuNtA1Xh0+K8xdf4hHFqv2ig=; b=TxBiXQlNSRt9mRxv+2tjClRbm6MN+DjOqi6QQELNlkPObN3dxWl4Q9uNpcS3M68REu LGDDEcLKxK7eB25Y5qenwyEFU4CTTVZ01yG7kfZdeDFKGUI+pNfF9JvbxhAdzplI7hTI z+PiVttmagrc7WvbTBCoaKo5qaLRCyL4m7w64= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=BSkhZZQ6IIqtFNbk5YmTuNtA1Xh0+K8xdf4hHFqv2ig=; b=bKWZuiNUmU6c20NlCzXCKH1jw0SAYBjU9zKfnWBIkz6nAnGAvabITzvNu7RRa5EPhN NKeXCd5wx0qJgnCjRdWblP1uoVgV3bI8Xy6K7pUbIEiqwOK60m37UfNjePHMXC4ArFjr LFq4wNNdyHfJFM5H33a2VgkIZt6Ke3lR03A9F0uBvoyxF+lTx8hX1zuTSOo/IYWzw8N9 Rbibf6afmnKKvbvs3hk4Aoz1EFlToHMFaSkmqmSnGor6s6wp3iEE32QYbel1VyjwaY/p bkpnqO8BXA6sg2k2XZShLMhK3RrwQRFCvBTGp3emQXQ9ZvV6rgaGNPSxsPUQIhZFUZe2 myag== X-Gm-Message-State: ALoCoQlrk0nE4yps6vGZjsTepdC9uybx1OkiG+EBBreVRT/x3xGwU1p70URfqfKDEzrbdy0Xdraq MIME-Version: 1.0 X-Received: by 10.13.199.130 with SMTP id j124mr6470777ywd.70.1446835382454; Fri, 06 Nov 2015 10:43:02 -0800 (PST) Received: by 10.129.109.136 with HTTP; Fri, 6 Nov 2015 10:43:02 -0800 (PST) Date: Fri, 6 Nov 2015 10:43:02 -0800 Message-ID: Subject: Zookeeper down before query starts/after query finishes From: Hsuan Yi Chu To: dev@drill.apache.org Content-Type: multipart/alternative; boundary=001a114da6ea05326e0523e39d50 --001a114da6ea05326e0523e39d50 Content-Type: text/plain; charset=UTF-8 My understanding is : Before query starts/After query finishes, Foreman will put/delete running query profiles in zookeeper. However, if zookeeper is down before the put/delete is successful, Drill would be blocked at the put/delete operation. See https://issues.apache.org/jira/browse/DRILL-3751 I think it is not quite right to let Drill just wait for Zookeeper to respond. Does it make sense to use "time-out" here? --001a114da6ea05326e0523e39d50--