[
https://issues.apache.org/jira/browse/HBASE-12684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jurriaan Mous updated HBASE-12684:
----------------------------------
Attachment: HBASE-12684.patch
First suggestion for AsyncRpcClient to jumpstart this issue.
- Based on Netty 4. Dependency was already present.
- The AsyncRpcClient is set as the default client in this patch.
Todo:
- AsyncCall could be integrated with Call. Need to check rpcTimeout code.
- More duplicated code with RpcClientImpl could be abstracted.
- Tests that run with RpcClientImpl would need a AsyncRpcClient version.
Question:
- Will RpcClientImpl live on after this issue or should RpcClientImpl be
removed with the arrival of AsyncRpcClient? This question affects what work is
to be done next.
> Add new AsyncRpcClient
> ----------------------
>
> Key: HBASE-12684
> URL: https://issues.apache.org/jira/browse/HBASE-12684
> Project: HBase
> Issue Type: Improvement
> Components: Client
> Reporter: Jurriaan Mous
> Attachments: HBASE-12684.patch
>
>
> With the changes in HBASE-12597 it is possible to add new RpcClients. This
> issue is about adding a new Async RpcClient which would enable HBase to do
> non blocking protobuf service communication.
> Besides delivering a new AsyncRpcClient I would also like to ask the question
> what it would take to replace the current RpcClient? This would enable to
> simplify async code in some next issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
