Bryan Duxbury wrote:
So, you created a brand-new RPC framework?
No. hbase continues to use the bulk of the hadoop RPC'ing mechanism.
Just the hadoop RPC serialization class was customized making it so
types that are popular in hbase communications are identified by a
single-byte code rather than by classname-as-String. The resources
consumed passing the classname-as-String with accompanying
encoding/decoding of bytes and getting of Class from name would dwarf
that needed handling the payload particularly when the payload was small
(Infrequently used Writables or new Writables such as a new user-created
row filter will be passed using the classname-as-String mechanism).
I'll change the issue description so its clearer what has been changed.
St.Ack
