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 27368200BB3 for ; Wed, 2 Nov 2016 12:59:00 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 26070160B0C; Wed, 2 Nov 2016 11:59:00 +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 9C974160AFB for ; Wed, 2 Nov 2016 12:58:59 +0100 (CET) Received: (qmail 68709 invoked by uid 500); 2 Nov 2016 11:58:58 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 68583 invoked by uid 99); 2 Nov 2016 11:58:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Nov 2016 11:58:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 9DB9D2C0276 for ; Wed, 2 Nov 2016 11:58:58 +0000 (UTC) Date: Wed, 2 Nov 2016 11:58:58 +0000 (UTC) From: "Yu Li (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-16991) Make the initialization of AsyncConnection asynchronous MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 02 Nov 2016 11:59:00 -0000 [ https://issues.apache.org/jira/browse/HBASE-16991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628732#comment-15628732 ] Yu Li commented on HBASE-16991: ------------------------------- It seems to me in UT cases we are still using blocking mode (future.get) although we already have {{createAsyncConnection}} returning a CompletableFuture, mind take use of it and make the UT an example of fully asynchronous? Another question is that for blocking mode we no longer cache the connections for customer and depend on recommending user to only call create connection method once inside a single jvm process (honestly I don't even think this is a good idea...), but shall we follow the same pattern for async connections? If so we always have to block at the first time of getting connection although the implementation is non-blocking? Thanks. > Make the initialization of AsyncConnection asynchronous > ------------------------------------------------------- > > Key: HBASE-16991 > URL: https://issues.apache.org/jira/browse/HBASE-16991 > Project: HBase > Issue Type: Sub-task > Components: Client > Affects Versions: 2.0.0 > Reporter: Duo Zhang > Assignee: Duo Zhang > Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-16991.patch > > > Now the ConnectionFactory.createAsyncConnection is still blocking. We should make it return a CompletableFuture to make the async client fully asynchronous. -- This message was sent by Atlassian JIRA (v6.3.4#6332)