Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: error (athena.apache.org: local policy)
From: Jurriaan Mous <jurmous@jurmo.us>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_92F0622A-FF1F-4D3B-B12E-ABDC9D23E099"
Subject: Async RpcClient
Message-Id: <0669F82C-2D2A-41C3-A7E6-410C21CCF627@jurmo.us>
Date: Wed, 17 Dec 2014 18:32:26 +0100
To: user@hbase.apache.org
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2063\))

--Apple-Mail=_92F0622A-FF1F-4D3B-B12E-ABDC9D23E099
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

I have been working on a Netty 4 based async HBase client to fit better =
within the event driven server I have been developing. - =
https://github.com/jurmous/async-hbase-client/tree/HBase-0.99 =
<https://github.com/jurmous/async-hbase-client/tree/HBase-0.99>=20

Recently I have been submitting some patches to make it easier to switch =
out the RpcClient of HBase. This to enable HBase to use the client =
itself in all communication. I wanted to do this to use the tests on =
HBase to check if the client was solid on all edge cases but also to =
enable HBase to possibly migrate to an async client. These were =
committed on master and branch-1
https://issues.apache.org/jira/browse/HBASE-12597 =
<https://issues.apache.org/jira/browse/HBASE-12597>
https://issues.apache.org/jira/browse/HBASE-12684 =
<https://issues.apache.org/jira/browse/HBASE-12684>

Now I am at the next step where I want to contribute back the =
AsyncRpcClient itself.=20

I have opened this issue to add AsyncRpcClient:
https://issues.apache.org/jira/browse/HBASE-12684 =
<https://issues.apache.org/jira/browse/HBASE-12684>
In the current patch the new async client is the default.

3 questions:

Can anyone with a proper Kerberos setup test if the async client works? =
SASL Digest auth works but I haven=E2=80=99t tested Kerberos yet.=20

Can anyone with know-how on benchmarking test what the performance of =
this client is compared to the current client? The performance should of =
course be great in all relevant metrics will it ever be the main client.=20=


What will we do with the old RpcClient if the async RpcClient is =
introduced? It would be great to remove it so hbase can internally base =
anything async (like AsyncProcess) on the async RPC client and this =
would not be possible with an also supported sync RPC client. A possible =
route is to make AsyncRpcClient an option on 1.x and a default on 2.0 =
branch where we remove the old client.=20

When the new AsyncRpcClient will be the default it is possible to =
introduce callback variants of the Table, Scanner and Admin methods and =
possibly deprecate batch and other AsyncProcess based calls to replace =
it with a more flexible batch callback implementation.=20

Thanks,
Jurriaan


--Apple-Mail=_92F0622A-FF1F-4D3B-B12E-ABDC9D23E099--