If zookeeper isn`t invalidating the client`s cache, then what is the
actual use of a zookeeper session? Is it needed only to lookup
region-location of the "root-tablet" of META table, which is later used
to recursively scan the entire META table ?
Can`t that just be a lookup query to zookeeper, instead of a session ?
I`ve looked into the Bigtable paper; the above use-case seems to be the
only one mentioned. Am I missing something ?
Thanks,
Naresh.
On 10/01/2010 09:40 PM, Jonathan Gray wrote:
Yes. RegionServers will throw a NotServingRegionException. This, in turn,
will cause the client to grab the location from META again.
-----Original Message-----
From: Naresh Rapolu [mailto:[email protected]]
Sent: Friday, October 01, 2010 5:35 PM
To: [email protected]
Subject: Client`s cache invalidation
Hello,
How does the client`s cache of "region-location"( .META table), get
invalidated when a region-server splits regions ? Does Zookeeper abort
the client session or inform it of staleness ? How is consistency
ensured in the time interval between splits being registered in .META
table and client cache being refreshed ? I`m guessing, the region-
server
would reject operations on rows it isn`t responsible for. Am I correct
?
Thanks,
Naresh.
