[
https://issues.apache.org/jira/browse/HBASE-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933759#action_12933759
]
Lars George commented on HBASE-2357:
------------------------------------
Ah this is nice! I had asked this many times and insinuated something like that
to avoid that dreaded "region is a goner for a while until redeployed" in high
availability environments. Using a consensus brings us into the realm of using
a Dynamo like RegionServer architecture. With all the pros and cons, the latter
being if a strict consistency is asked for then you pay a performance penalty.
That is the case with any other open source projects implementing "R+W>N".
Can't we employ ZooKeeper for this somehow?
I love it!
> Coprocessors: 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: HBase
> Issue Type: Sub-task
> 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.
