[
https://issues.apache.org/jira/browse/HBASE-8104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608541#comment-13608541
]
Enis Soztutar commented on HBASE-8104:
--------------------------------------
In your case, you have to ensure two conditions:
(1) Only one master cluster is active at any given time.
(2) Data is not read from one cluster, unless all the data is replicated from
the other cluster.
Achieving (1) is easy. (2) might not even be possible if you do not have
synchronous replication, since eventual updates might not be propagated for
extended periods of time.
> HBase consistency and availability after replication
> ----------------------------------------------------
>
> Key: HBASE-8104
> URL: https://issues.apache.org/jira/browse/HBASE-8104
> Project: HBase
> Issue Type: New Feature
> Affects Versions: 0.94.3
> Reporter: Brian Fu
> Priority: Critical
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> HBase consistency and availability after replication
> Scene as follows:
> 1. There are two HBase clusters are the Master clusters and Slave Clusters.
> two clusters replication function is open.
> 2. if master cluster have problems, so all write and read request switching
> to the slave cluster.
> 3. After a period of time ,we need to switch back to the Master cluster,
> there will be a part of the data is inconsistent, lead to this part of the
> data is not available.
> This feature is particularly important for providing online services HBase
> cluster.
> So, I want through a write-back program to keep the data consistency, then to
> improve HBase availability.
> we will provide a patch for this function.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
