hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Rodionov <vrodio...@carrieriq.com>
Subject RE: Region server failover
Date Thu, 13 Mar 2014 21:10:14 GMT
People usually add some code on top to mitigate down time.
for non blocking writes - add in memory or persistent queue
for non blocking reads - add intermediate cache.

Best regards,
Vladimir Rodionov
Principal Platform Engineer
Carrier IQ, www.carrieriq.com
e-mail: vrodionov@carrieriq.com

From: Jeff Storey [storey.jeff@gmail.com]
Sent: Thursday, March 13, 2014 1:54 PM
To: user@hbase.apache.org
Subject: Re: Region server failover

Thanks for the quick reply. It looks like this feature is in the works.

What are people doing in the absence of this feature? Simply allowing the

On Thu, Mar 13, 2014 at 4:51 PM, Ted Yu <yuzhihong@gmail.com> wrote:

> Take a look at HBASE-10070:
> HBase read high-availability using eventually consistent region replicas
> Cheers
> On Thu, Mar 13, 2014 at 1:49 PM, Jeff Storey <storey.jeff@gmail.com>
> wrote:
> > I'm still somewhat new to HBase and I'm trying to understand
> possibilities
> > for region server failover. If I have a region server that goes down, it
> > looks like I won't have any access to that region's data until a backup
> > server comes online. I read that I can reduce the zookeeper timeout to
> > minimize that time down, but in a system that is meant to be highly
> > available, it seems like this could be cause for concern since a portion
> of
> > the data will be entirely inaccessible.
> >
> > Is there a way to have a secondary read-only region server that becomes
> the
> > new primary region server in the event of a failure? This way that data
> > will always be accessible unless all of the region server backups fail?
> Or
> > are there other ways to replicate region data to avoid loss of access for
> > possibly several minutes to that data if the server goes down?
> >
> > Thanks,
> > Jeff
> >

Confidentiality Notice:  The information contained in this message, including any attachments
hereto, may be confidential and is intended to be read only by the individual or entity to
whom this message is addressed. If the reader of this message is not the intended recipient
or an agent or designee of the intended recipient, please note that any review, use, disclosure
or distribution of this message or its attachments, in any form, is strictly prohibited. 
If you have received this message in error, please immediately notify the sender and/or Notifications@carrieriq.com
and delete or destroy any copy of this message and its attachments.

View raw message