Hey, You might be interested in the "shadow replica" discussion in the dev list. The aim is to lower the mttr incase of a failure. Here is the link to the discussion[1] and the jira[2]. These are very much relevant to what you are looking for.
[1] http://apache-hbase.679495.n3.nabble.com/Shadow-Regions-Read-Replicas-td4053313.html [2] https://issues.apache.org/jira/browse/HBASE-10070 - Bharath On Sun, Mar 30, 2014 at 10:31 PM, Jeff Storey <storey.j...@gmail.com> wrote: > In evaluating strategies for minimizing downtime when a region server > fails, in addition to the common approaches such as lowering the zookeeper > timeout, is it possible to use replication to improve availability (at the > cost of consistency) for reads? > > I'm still getting more familiar with the HBASE api, but my thought would be > to do something like: > > - attempt read from the primary cluster > - if read fails because of downed region server, read from slave cluster > (understanding that the read may be a little bit stale) > > I wouldn't expect this to happen too frequently, but in a case where I > would rather return slightly stale data rather than no data, is this a > viable approach? > > I'm not sure how the java api deals with reading from a region server that > is in the process of failing over? Is there a way to detect that? > > Thanks for the help. > -- Bharath Vissapragada <http://www.cloudera.com>
