Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A4ADF10FF8 for ; Fri, 28 Nov 2014 13:30:13 +0000 (UTC) Received: (qmail 73315 invoked by uid 500); 28 Nov 2014 13:30:12 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 73166 invoked by uid 500); 28 Nov 2014 13:30:12 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 72903 invoked by uid 99); 28 Nov 2014 13:30:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Nov 2014 13:30:12 +0000 Date: Fri, 28 Nov 2014 13:30:12 +0000 (UTC) From: "Jurriaan Mous (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-12597) Add RpcClient interface and enable changing of RpcClient implementation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jurriaan Mous created HBASE-12597: ------------------------------------- Summary: Add RpcClient interface and enable changing of RpcClient implementation Key: HBASE-12597 URL: https://issues.apache.org/jira/browse/HBASE-12597 Project: HBase Issue Type: Improvement Components: Client Reporter: Jurriaan Mous Currently HConnectionImplementation works with the included RpcClient which is a direct implementation and not defined by an interface. It would be great to be able to swap out the default RpcClient with another implementation which can also be controlled by the default HConnectionImplementation. Suggested changes: - Create a RpcClient interface which defines all the ways HConnectionImplementation interacts with an RPC client. Like getting a blocking protobuf service interface or closing the client. - Define which RpcClient implementation to construct by setting a configuration variable which defaults to the current RpcClient. - Possibly create an abstract RpcClient class to only load all the basic Rpc layer configurations to be used in an implementation. Why? It enables experimentation with RpcClients which could enable new features or could be more performant than the included client. I created a new RpcClient implementation based on Netty which can also be called asynchronously. It would be great to also be able to use this RpcClient in all the default ways and tests to see if there are any issues with it. https://github.com/jurmous/async-hbase-client/ https://github.com/jurmous/async-hbase-client/blob/master/src/main/java/org/apache/hadoop/hbase/ipc/AsyncRpcClient.java -- This message was sent by Atlassian JIRA (v6.3.4#6332)