hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dagaev" <michael.dag...@gmail.com>
Subject Re: HTable Pooling Results
Date Wed, 17 Dec 2008 09:10:46 GMT
Maybe it makes sense to make the transport "pluggable". So we can
change it without having to modify the code.

On Wed, Dec 17, 2008 at 4:38 AM, Andrew Purtell <apurtell@yahoo.com> wrote:
> One reason I'd personally like to see another (binary) wire
> protocol for communicating between the clients, master, and
> regionservers is HBASE-1015:
>
>    https://issues.apache.org/jira/browse/HBASE-1015
>
> Maybe I'll have some time to work on this soon in 2009.
>
>   - Andy
>
>
>> From: Michael Dagaev <michael.dagaev@gmail.com>
>> Subject: Re: HTable Pooling Results
>> To: hbase-user@hadoop.apache.org
>> Date: Tuesday, December 16, 2008, 1:19 PM
>> When I started testing it was pretty obvious that the
>> synchronized commit of Htable actually serializes access
>> to the table, so pooling was a trivial solution to work
>> around the problem. It is good enough, however, I hope
>> that the RPC limitation will be fixed.
>>
>> I believe this is not a big deal from the technical
>> perspective but I can understand why it is not trivial.
>> It should be fixed by Hadoop. Hadoop do not want to fix
>> it, probably. Therefore, Hbase should consider an
>> alternative for Hadoop RPC and this is a big deal.
>>
>> M.
>
>
>
>
>

Mime
View raw message