[ https://issues.apache.org/jira/browse/HBASE-8104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13608509#comment-13608509 ]
Jieshan Bean commented on HBASE-8104: ------------------------------------- I think so, this is the only way we can do that. But I don't think we really need that. > 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