[
https://issues.apache.org/jira/browse/HBASE-11574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275672#comment-14275672
]
Devaraj Das edited comment on HBASE-11574 at 1/13/15 6:46 PM:
--------------------------------------------------------------
Patch for master for review. WIP patch - I am running the unit tests etc with
it at this point.
The high level on the patch:
* Introduces config knobs -
** hbase.meta.replicas.use defaulting to false. If true, then the client
will try to use replicas of the meta. This is set to false explicitly on the
master, regionservers & hbck. They should always go to the primary for
reads/writes.
** hbase.meta.replica.count defaulting to 1. This would control how many
replicas of the meta are created.
* The meta replicas are assigned by the master after the primary is assigned.
* The meta edits are not replicated yet to the secondary replicas. The primary
flushes sooner (the flush is triggered if a meta edit is older than 5 minutes)
in order for the secondaries to pick up the new edits from the storefiles.
* HBCK is aware of the meta replicas and will try to fix issues to do with
fewer/excess replicas assigned
* UI changes to list the replicas is done
* Unit tests & IT test present
was (Author: devaraj):
Patch for master for review. I am running the unit tests etc with it at this
point.
> hbase:meta's regions can be replicated
> --------------------------------------
>
> Key: HBASE-11574
> URL: https://issues.apache.org/jira/browse/HBASE-11574
> Project: HBase
> Issue Type: Sub-task
> Reporter: Enis Soztutar
> Assignee: Devaraj Das
> Fix For: 1.1.0
>
> Attachments: 11574-1.txt, meta-replicas-0.98.zip
>
>
> As mentioned elsewhere, we can leverage hbase-10070 features to create
> replicas for the meta tables regions so that:
> 1. meta hotspotting can be circumvented
> 2. meta becomes highly available for reading
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
