hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2357) Add read-only region replicas (slaves) for availability and fast region recovery
Date Sat, 27 Mar 2010 22:25:27 GMT

    [ https://issues.apache.org/jira/browse/HBASE-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850591#action_12850591

Andrew Purtell commented on HBASE-2357:

Minor clarification

bq. But with a consensus protocol, read load can be spread as is the intent of this issue
and yet the data is still strongly consistent

_at any time on any region server hosting the region (or a replica)_

so an ICV is atomic no matter what region server any client is talking to, for example.

> Add read-only region replicas (slaves) for availability and fast region recovery
> --------------------------------------------------------------------------------
>                 Key: HBASE-2357
>                 URL: https://issues.apache.org/jira/browse/HBASE-2357
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: master, regionserver
>            Reporter: Todd Lipcon
> I dont plan on working on this in the short term, but the idea is to extend region ownership
to have two modes. Each region has one primary region server and N slave region servers. The
slaves would follow the master (probably by streaming the relevant HLog entries directly from
it) and be able to serve stale reads. The benefit is twofold: (a) provides the ability to
spread read load, (b) enables very fast region failover/rebalance since the memstore is already
nearly up to date on the slave RS.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message