hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ning Li" <ning.li...@gmail.com>
Subject Re: Sequence Number for Cache Flush
Date Tue, 03 Jun 2008 17:32:08 GMT
On 6/3/08, stack <stack@duboce.net> wrote:
> Does tupdatesLock prevent the hole you describe?  Flushing must hold the
> updatesLock write lock to proceed.  Updates take out a read lock on
> updatesLock.  All updates will have gone into the WAL and into the memcache
> before the read lock is released.

Do you mean the updatesLock's write lock acquired before the calls to
HStore.snapshot()? But the sequence number is taken after the write
lock is released, right?


View raw message