From issues-return-56345-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Tue Jan 30 14:50:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 6CFE618061A for ; Tue, 30 Jan 2018 14:50:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 5CD51160C53; Tue, 30 Jan 2018 13:50:04 +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 A4946160C42 for ; Tue, 30 Jan 2018 14:50:03 +0100 (CET) Received: (qmail 83247 invoked by uid 500); 30 Jan 2018 13:50:02 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 83238 invoked by uid 99); 30 Jan 2018 13:50:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jan 2018 13:50:02 +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 7C3B718034D for ; Tue, 30 Jan 2018 13:50:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 9ZmyhWfqKDQv for ; Tue, 30 Jan 2018 13:50:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 52A4B5FBEB for ; Tue, 30 Jan 2018 13:50:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 8DCA5E01AA for ; Tue, 30 Jan 2018 13:50:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 13B9721301 for ; Tue, 30 Jan 2018 13:50:00 +0000 (UTC) Date: Tue, 30 Jan 2018 13:50:00 +0000 (UTC) From: "Roman Guseinov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (IGNITE-7192) JDBC: support FQDN to multiple IPs during connection establishment 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/IGNITE-7192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16340659#comment-16340659 ] Roman Guseinov edited comment on IGNITE-7192 at 1/30/18 1:49 PM: ----------------------------------------------------------------- [~alexey.tank2], please review the PR ([https://github.com/apache/ignite/pull/3439 )|https://github.com/apache/ignite/pull/3439:]). Thanks. was (Author: guseinov): [~alexey.tank2], please review the PR ([https://github.com/apache/ignite/pull/3439)|https://github.com/apache/ignite/pull/3439):]. Thanks. > JDBC: support FQDN to multiple IPs during connection establishment > ------------------------------------------------------------------ > > Key: IGNITE-7192 > URL: https://issues.apache.org/jira/browse/IGNITE-7192 > Project: Ignite > Issue Type: Improvement > Components: jdbc > Affects Versions: 2.1 > Reporter: Alexey Popov > Assignee: Roman Guseinov > Priority: Major > Labels: pull-request-available > > Thin JDBC driver may have FQDN (host name) at a connection string. > Currently, it resolves this FQDN to one IP and tries to connect to this IP only. > It is better to try to connect to multiple IPs one-by-one if DNS returns multiple A-records (FQDN can be resolved to several IPs) until successful connection. It could give a simple fallback option for the JDBC thin driver users. > A similar functionality is already implemented in ODBC driver. -- This message was sent by Atlassian JIRA (v7.6.3#76005)