1) you can use replication metrics info such as:ageOfLastShippedOp,
timeStampsOfLastShippedOp, sizeOfLogQueue ageOfLastAppliedOp, and
timeStampsOfLastAppliedOp to figure out the lag.
2) with my best knowledge, the replication won't be together with snapshot.
That is the peers won't know there is a restore occurred on primary. So a
user must take care it manually. the VerifyReplication tool may be
helpful to identify which data (boundary by timestamps) is mismatch, so the
copyTable doesn't have to copy the whole table
On Mon, Oct 28, 2013 at 12:07 PM, hdev ml <[EMAIL PROTECTED]> wrote:
> Hello all,
> I have a couple of questions for HBase.
> 1. Is there any way to find out by how much time the replication is lagging
> on the peer cluster or even primary cluster is ok.
> 2. Say replication is going on for some time for a table and then you
> restore a snapshot on the Primary. Would replication catch up with the
> restore snapshot? Or do I have to treat that as replicating from scratch,
> 1. disable peer
> 2. restore snapshot on primary
> 3. copyTable upto disable timestamp
> 4. enable peer
> Any help is appreciated.