[
https://issues.apache.org/jira/browse/HBASE-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422872#comment-13422872
]
terry zhang commented on HBASE-6453:
------------------------------------
Hiļ¼Stack. I think we can use point in time feature with Snapshots feature
(HBASE-6055) in below case.
1. Master cluster in data center China do a Snapshot at Time A
2. copy the Snapshot to Slave cluster in data center US and Set Replication
Time stamp to A
3. Restore snapshots (HBASE-6230 ) for Slave cluster and start replication.
Them Slave cluster data will be as same as Master Cluster . And data is more
safe and US user can visit Slave cluster for getting or scanning data to
decrease the stress for China data center. Enable replication can not control
the accurate time so may be it will lose some data or replicate some useless
data. Mysql also has point in time/position feature in it replication
Framework. It is very convenience for data center administrate to use.
We can give some better name for this operation cause I am not good at naming
...
> Hbase Replication point in time feature
> ---------------------------------------
>
> Key: HBASE-6453
> URL: https://issues.apache.org/jira/browse/HBASE-6453
> Project: HBase
> Issue Type: New Feature
> Components: replication
> Affects Versions: 0.94.0
> Reporter: terry zhang
> Assignee: terry zhang
> Attachments: hbase-6453-v1.patch
>
>
> Now we can not control when hbase replication start to work. this patch
> support we set a time stamp filter . All the row which is below this time
> stamp will not be replicated. We also can delete and show this time stamp in
> hbase shell if we want to change it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
