hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Storey <storey.j...@gmail.com>
Subject Re: Region server failover
Date Thu, 13 Mar 2014 21:03:13 GMT
Excellent, thanks!


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

> See this presentation from last year's HBaseCon :
>
> http://www.slideshare.net/cloudera/internals-session-2
>
> Cheers
>
>
> On Thu, Mar 13, 2014 at 1:54 PM, Jeff Storey <storey.jeff@gmail.com>
> wrote:
>
> > 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
> > downtime?
> >
> >
> > 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
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message