Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Tue, 12 May 2015 21:03:00 +0000 (UTC)
From: "Daniel Barclay (Drill) (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12829327.1431464287000.93450.1431464580004@Atlassian.JIRA>
In-Reply-To: <JIRA.12829327.1431464287000@Atlassian.JIRA>
References: <JIRA.12829327.1431464287000@Atlassian.JIRA>
 <JIRA.12829327.1431464287478@arcas>
Subject: [jira] [Issue Comment Deleted] (DRILL-3039) Trying to connect to
 non-existent Zookeeper seems to try indefinitely
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DRILL-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Barclay (Drill) updated DRILL-3039:
------------------------------------------
    Comment: was deleted

(was: (To check for similar cases, set breakpoints on ConfigException constructors and start Drill.))

> Trying to connect to non-existent Zookeeper seems to try indefinitely
> ---------------------------------------------------------------------
>
>                 Key: DRILL-3039
>                 URL: https://issues.apache.org/jira/browse/DRILL-3039
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Daniel Barclay (Drill)
>
> Trying to make a JDBC connection using a JDBC URL of "jdbc:drill:", which causes defaulting to a "zk" configuration parameter value of "localhost:2181", when there is no Zookeeper running at that address doesn't fail quickly, but seems to cause trying indefinitely.  
> (There's no response back to the JDBC level, and turning up logging verbosity shows continued activity (every second or so) in org.apache.zookeeper code).


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)