[
https://issues.apache.org/jira/browse/HBASE-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831823#action_12831823
]
ryan rawson commented on HBASE-2197:
------------------------------------
I am not generally a fan of depending on files and region layout. We need to
have a system where we can bring up a cluster immediately and get new edits in
then pull in the rest of them as fast as possible. I think the latter process
should be out of bounds, ie: lets keep the replication core in HRS really
small, then add value on and around it, possibly with some HRS hooks if
necessary.
As for the random read issue, we should highly consider removing that code.
> Start replication from a point in time
> --------------------------------------
>
> Key: HBASE-2197
> URL: https://issues.apache.org/jira/browse/HBASE-2197
> Project: Hadoop HBase
> Issue Type: Sub-task
> Reporter: Jean-Daniel Cryans
> Fix For: 0.21.0
>
>
> One way to set up a cluster for replication is to distcp all files then start
> the replication. We need a way to make sure we don't miss any edits by being
> able to start a process that reads old log files from a defined point in time
> and send them to a specific slave cluster and then catch up with normal
> replication.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
