Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3302710EF7 for ; Tue, 29 Oct 2013 01:04:25 +0000 (UTC) Received: (qmail 7324 invoked by uid 500); 29 Oct 2013 01:04:23 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 7237 invoked by uid 500); 29 Oct 2013 01:04:22 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 7229 invoked by uid 99); 29 Oct 2013 01:04:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Oct 2013 01:04:21 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hdevml@gmail.com designates 209.85.128.174 as permitted sender) Received: from [209.85.128.174] (HELO mail-ve0-f174.google.com) (209.85.128.174) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Oct 2013 01:04:16 +0000 Received: by mail-ve0-f174.google.com with SMTP id pa12so5078453veb.5 for ; Mon, 28 Oct 2013 18:03:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=jFhRnH7uY9r2oIyyt4lgA3d48550heCydXt4xjNTVQ8=; b=aRo3iRxkAt1ZJnsy8y4hV79Dg+WrvOBGpU7vpX63voJmMr3KrQZiErxcx7tBKVAA/z oZZpTiHVgiAyivQaAqRtbC81R+syF7AeRgmzK65FMV9c3v2iaOrtUBvufF1UN+1No19f CCqDzUu12ErY7FhAAtJYeteNG6xr6dS0caaaw7FIpk1+f3mf0T8mVFc/9fnNijL4Q593 J7uZwQxaBVp6XWyvjdeR54YbonhVYLdLSW6Xmp81C24SOW+ZctppQ+1jGVkOZbL7HrPK UXNinlttY38iWOnC9itSqvNyvQqRGyo7Cp4L0E7x0mWpI3ZebOdrbmMYFHVOhn2NpNR4 IcFQ== MIME-Version: 1.0 X-Received: by 10.52.103.35 with SMTP id ft3mr13159716vdb.5.1383008635813; Mon, 28 Oct 2013 18:03:55 -0700 (PDT) Received: by 10.58.136.197 with HTTP; Mon, 28 Oct 2013 18:03:55 -0700 (PDT) In-Reply-To: References: Date: Mon, 28 Oct 2013 18:03:55 -0700 Message-ID: Subject: Re: HBase Replication Questions From: hdev ml To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=e89a8ff24d9b75862204e9d6ca89 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8ff24d9b75862204e9d6ca89 Content-Type: text/plain; charset=ISO-8859-1 Thanks Ted. Will take a look at it. On Mon, Oct 28, 2013 at 3:33 PM, Ted Yu wrote: > Please see also 'Replication Metrics' at the bottom of > http://hbase.apache.org/replication.html > > > On Mon, Oct 28, 2013 at 3:23 PM, hdev ml wrote: > > > Thanks Demai. Need to find out how to access HBase metrics. > > > > But thanks for your insights. > > Harshad > > > > > > On Mon, Oct 28, 2013 at 2:45 PM, Demai Ni wrote: > > > > > 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 > > > > > > Demai > > > > > > Demai > > > > > > > > > On Mon, Oct 28, 2013 at 12:07 PM, hdev ml 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, > > > > meaning > > > > > > > > 1. disable peer > > > > 2. restore snapshot on primary > > > > 3. copyTable upto disable timestamp > > > > 4. enable peer > > > > > > > > > > > > Any help is appreciated. > > > > > > > > Thanks > > > > > > > > Harshad > > > > > > > > > > --e89a8ff24d9b75862204e9d6ca89--