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 1DAA2200BC9 for ; Fri, 11 Nov 2016 09:20:01 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1C95C160AE4; Fri, 11 Nov 2016 08:20:01 +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 626E6160B01 for ; Fri, 11 Nov 2016 09:20:00 +0100 (CET) Received: (qmail 98213 invoked by uid 500); 11 Nov 2016 08:19:59 -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 97788 invoked by uid 99); 11 Nov 2016 08:19:59 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Nov 2016 08:19:59 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E3B032C4C7E for ; Fri, 11 Nov 2016 08:19:58 +0000 (UTC) Date: Fri, 11 Nov 2016 08:19:58 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DRILL-5015) As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 11 Nov 2016 08:20:01 -0000 [ https://issues.apache.org/jira/browse/DRILL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656487#comment-15656487 ] ASF GitHub Bot commented on DRILL-5015: --------------------------------------- Github user sohami commented on a diff in the pull request: https://github.com/apache/drill/pull/648#discussion_r87551861 --- Diff: exec/rpc/src/main/java/org/apache/drill/exec/rpc/InvalidConnectionInfoException.java --- @@ -0,0 +1,35 @@ +/** + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, software + * distributed under the License is distributed on an "AS IS" BASIS, + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + * See the License for the specific language governing permissions and + * limitations under the License. + */ +package org.apache.drill.exec.rpc; + +/** + * Exception class to differentiate errors due to malformed connection string from client + */ +public class InvalidConnectionInfoException extends RpcException { + static final org.slf4j.Logger logger = org.slf4j.LoggerFactory.getLogger(InvalidConnectionInfoException.class); + + private final String message; + + public InvalidConnectionInfoException(String message) { --- End diff -- Done > As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: DRILL-5015 > URL: https://issues.apache.org/jira/browse/DRILL-5015 > Project: Apache Drill > Issue Type: Bug > Components: Client - JDBC > Affects Versions: 1.8.0, 1.9.0 > Reporter: Sorabh Hamirwasia > Assignee: Sudheesh Katkam > > When trying to connect to a Drill cluster by specifying more than 1 drillbits to connect to, we always attempt to connect to only the first drillbit. > As an example, we tested against a pair of drillbits, but we always connect to the first entry in the CSV list by querying for the 'current' drillbit. The remaining entries are never attempted. > [root@pssc-60 agileSqlPerfTests]# /opt/mapr/drill/drill-1.8.0/bin/sqlline -u "jdbc:drill:schema=dfs.tmp;drillbit=pssc-61:31010,pssc-62:31010" -f whereAmI.q | grep -v logback > 1/1 select * from sys.drillbits where `current`; > +-----------------+------------+---------------+------------+----------+ > | hostname | user_port | control_port | data_port | current | > +-----------------+------------+---------------+------------+----------+ > | pssc-61.qa.lab | 31010 | 31011 | 31012 | true | > +-----------------+------------+---------------+------------+----------+ > 1 row selected (0.265 seconds) > Closing: org.apache.drill.jdbc.impl.DrillConnectionImpl > apache drill 1.8.0 > "a little sql for your nosql" > This property is meant for use by clients when not wanting to overload the ZK for fetching a list of existing Drillbits, but the behaviour doesn't match the documentation. > [Making a Direct Drillbit Connection | https://drill.apache.org/docs/using-the-jdbc-driver/#using-the-jdbc-url-format-for-a-direct-drillbit-connection ] > We need to randomly shuffle between this list and If an entry in the shuffled list is unreachable, we need to try for the next entry in the list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)