[
https://issues.apache.org/jira/browse/HBASE-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173906#comment-13173906
]
stack commented on HBASE-3523:
------------------------------
Breathing some life back into this issue:
Reasons for new client, updates:
+ The Jonathan Payne accounting of unaccounted off-heap socket buffers per
thread which makes our client OOME when lots of threads (HBASE-4956)
+ "complex", lots of layers, long-lived zk connection (not necessary on client?)
+ Should work against multiple versions of hbase (but that might be another
issue, an rpc issue... this issue could be distinct from rpc fixup?)
See also Lars comment here:
https://issues.apache.org/jira/browse/HBASE-5058?focusedCommentId=13173364&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13173364
> Rewrite our client (client 2.0)
> -------------------------------
>
> Key: HBASE-3523
> URL: https://issues.apache.org/jira/browse/HBASE-3523
> Project: HBase
> Issue Type: Brainstorming
> Reporter: stack
>
> Is it just me or do others sense that there is pressure building to redo the
> client? If just me, ignore the below... I'll just keep notes in here.
> Otherwise, what would the requirements for a client rewrite look like?
> + Let out InterruptedException
> + Enveloping of messages or space for metadata that can be passed by client
> to server and by server to client; e.g. the region a.b.c moved to server
> x.y.z. or scanner is finished or timeout
> + A different RPC? One with tighter serialization.
> + More sane timeout/retry policy.
> Does it have to support async communication? Do callbacks?
> What else?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
