[HBASE-9351] Connection capability negotiation

• Type: Brainstorming
• Status: Closed
• Priority: Major
• Resolution: Later
• Affects Version/s: 0.99.0
• Assignee: Unassigned
• Reporter: Andrew Kyle Purtell
• Created: 27/Aug/13 09:41
• Updated: 16/Jun/22 17:58
• Resolved: 12/May/14 03:49

Description

Would be useful to support negotiation at connection setup time beyond SASL. Consider:

Start with a default baseline profile. Both client and server sides can begin communicating immediately (or after SASL completes if security is active), with a baseline set of messages and codecs.

For more interesting use cases, support configuration messages that negotiate connection configuration going forward after both sides ack the changes: codec, configuration, compression. Any nack aborts the upgrade request and leaves both sides still in the default profile.

Should be a pluggable implementation. For example, codec implementations should be automatically discovered at runtime if shipped with the client or server, and the set of available options should be communicated to the other side.

Features like codecs should all be versioned themselves. Negotiation should be version aware, and decisionmaking on if a given pair of component versions are compatible should be delegated to the component.

Issue Links

• is related to: HBASE-9136 RPC side changes to have a different codec for server to client communication
• is related to: HBASE-9230 Fix the server so it can take a pure pb request param and return a pure pb result

Sub-Tasks

• Basic codec negotiation: Closed