Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1565813548.188051265831431670.JavaMail.jira@brutus.apache.org>
Date: Wed, 10 Feb 2010 19:50:31 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-2197) Start replication from a point in
 time
In-Reply-To: <1764220367.139211265681848261.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832151#action_12832151 ] 

Andrew Purtell commented on HBASE-2197:
---------------------------------------

{quote}
bq. My expectation as a user is that I would turn on replication and then do a MR job to transfer already stored data from the source cluster to the new peer.
So we could ship a MR that takes in input a table and that outputs to a peer cluster, that's how you see it?
{quote}

Something generic we can provide would be helpful. A TOF that supports some notion of remote table? 


> 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.