hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lars hofhansl <la...@apache.org>
Subject Re: RowLocks
Date Thu, 29 Aug 2013 04:22:59 GMT
Specifically the API has been removed because it had never actually worked correctly.


Rowlocks are used by RegionServers for intra-region operations.
As such they are ephemeral, in-memory constructs, that cannot reliably outlive a single RPC
request.
The HTable rowlock API allowed you to create a rowlocks and hold it over multiple RPCs, which
would break if f.e. a region is moved or split.

-- Lars
________________________________
From: Ted Yu <yuzhihong@gmail.com>
To: "user@hbase.apache.org" <user@hbase.apache.org> 
Sent: Wednesday, August 28, 2013 8:01 PM
Subject: Re: RowLocks


The API is no longer a public API

Thanks


On Wed, Aug 28, 2013 at 7:58 PM, Michael Segel <michael_segel@hotmail.com>wrote:

> Ted,
> Can you clarify...
> Do you mean the API is no longer a public API, or do you mean no more RLL
> for atomic writes?
>
> On Aug 28, 2013, at 5:18 PM, Ted Yu <yuzhihong@gmail.com> wrote:
>
> > RowLock API has been removed in 0.96.
> >
> > Can you tell us your use case ?
> >
> >
> > On Wed, Aug 28, 2013 at 3:14 PM, Kristoffer Sjögren <stoffe@gmail.com
> >wrote:
> >
> >> Hi
> >>
> >> About the internals of locking a row in hbase.
> >>
> >> Does hbase row locks map one-to-one with a locks in zookeeper or are
> there
> >> any optimizations based on the fact that a row only exist on a single
> >> machine?
> >>
> >> Cheers,
> >> -Kristoffer
> >>
>
> The opinions expressed here are mine, while they may reflect a cognitive
> thought, that is purely accidental.
> Use at your own risk.
> Michael Segel
> michael_segel (AT) hotmail.com
>
>
>
>
>
>

Mime
View raw message