[HBASE-3523] Rewrite our client (client 2.0)

• Type: Brainstorming
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Assignee: Unassigned
• Reporter: Michael Stack
• Created: 10/Feb/11 23:41
• Updated: 12/Jun/22 17:28
• Resolved: 11/Apr/15 01:16

Description

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?

Issue Links

• incorporates: HBASE-3584 Allow atomic put/delete in one call
• incorporates: HBASE-2408 Add envelope around client<->server communication so can pass state along w/ data during interchange
• is related to: HBASE-2182 rpc/ipc refactor; x-version compatibility, nio, async, enveloping, sane timeouts, etc.
• relates to: HBASE-2937 Facilitate Timeouts In HBase Client
• relates to: HBASE-1844 The ability to set a (global) client side timeout
• relates to: HBASE-4956 Control direct memory buffer consumption by HBaseClient
• relates to: HBASE-1843 HBase Client Configuration -- Millisecond Pauses and very few Retries (s)
• relates to: HBASE-3382 Make HBase client work better under concurrent clients
• relates to: HBASE-2170 hbase lightweight client library as a distribution