Hi,
We are running into a case that if the region server that serves meta table is
down, all request will timeouts because region lookup is not available. At this
time, master is also not able to update meta table.
It seems that regions that serve root and meta are the single point of failure
On 9/4/12 3:07 PM, Stack st...@duboce.net wrote:
On Tue, Sep 4, 2012 at 2:52 PM, Gen Liu ge...@zynga.com wrote:
We are running into a case that if the region server that serves meta
table is down, all request will timeouts because region lookup is not
available.
Only requests to .META. fail
block all threads?
Any thought is appreciated. Thanks.
Gen Liu
On 8/18/12 12:33 PM, Stack st...@duboce.net wrote:
On Fri, Aug 17, 2012 at 4:42 PM, Gen Liu ge...@zynga.com wrote:
I assume block cache store compressed data,
Generally its not, not unless you use block encoding.
Can you be more specific on this? Are you talking about
https
Hi,
I'm dealing with latency sensitive random read application on HBase. It seems
that block cache is designed for sequential read. I use the default 64k block
size which is much bigger than my row (10k after GZ compression).
I assume block cache store compressed data, one block can hold 6
Hi,
Hbase thrift doesn't expose setAutoFlush interface. I ran thrift out of the
Hbase cluster. I want to have a client side write buffering on the Thrift
server.
So I change the ThriftServer.java, and add a setAutoFlush(false) as follows:
if (!tables.containsKey(table)) {
boolean autoFlush =
administrators recover the cluster, is there any data lost
if master is dead for a while, etc.
Any link, suggestion, help will be appreciated. Thanks.
Gen Liu
