Return-Path: X-Original-To: apmail-drill-issues-archive@minotaur.apache.org Delivered-To: apmail-drill-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D275D18975 for ; Wed, 24 Feb 2016 19:00:20 +0000 (UTC) Received: (qmail 56047 invoked by uid 500); 24 Feb 2016 19:00:20 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 55977 invoked by uid 500); 24 Feb 2016 19:00:20 -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 55897 invoked by uid 99); 24 Feb 2016 19:00:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Feb 2016 19:00:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 652B72C1F6E for ; Wed, 24 Feb 2016 19:00:20 +0000 (UTC) Date: Wed, 24 Feb 2016 19:00:20 +0000 (UTC) From: "Jacques Nadeau (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DRILL-4433) Unnecessary entries created in ZK when a jdbc application uses a wrong connection URL 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-4433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163528#comment-15163528 ] Jacques Nadeau commented on DRILL-4433: --------------------------------------- I would add an additional note here, as well: ZK is only used by the client to determine what nodes are available, not maintain cluster cohesion. As such, it should be fast and not a long-lasting connection. I think that as part of this change we should also use a faster mechanism to doing this lookup. > Unnecessary entries created in ZK when a jdbc application uses a wrong connection URL > -------------------------------------------------------------------------------------- > > Key: DRILL-4433 > URL: https://issues.apache.org/jira/browse/DRILL-4433 > Project: Apache Drill > Issue Type: Bug > Components: Client - JDBC > Reporter: Rahul Challapalli > > commit # : 6d5f4983003b8f5d351adcb0bc9881d2dc4c2d3f > commit date : Feb 22, 2016 > In my JDBC application, I accidentally used an invalid connection string like below > {code} > jdbc:drill:zk=x.x.x.x:5181/zkroot-blah/cluster-name > {code} > While drill correctly reported an "No DrillbitEndpoint can be found error", I also observed that it created an entry in zookeeper by the name "zkroot-blah". There seems to be no reason for doing this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)