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 8C10010718 for ; Thu, 1 Aug 2013 22:04:40 +0000 (UTC) Received: (qmail 81656 invoked by uid 500); 1 Aug 2013 22:04:38 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 81613 invoked by uid 500); 1 Aug 2013 22:04:38 -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 81605 invoked by uid 99); 1 Aug 2013 22:04:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Aug 2013 22:04:38 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates 209.85.212.178 as permitted sender) Received: from [209.85.212.178] (HELO mail-wi0-f178.google.com) (209.85.212.178) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Aug 2013 22:04:34 +0000 Received: by mail-wi0-f178.google.com with SMTP id j17so97518wiw.5 for ; Thu, 01 Aug 2013 15:04:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=PVunhPpsyM4GFBjaa7QRpjXwMrFh1dmk1UVULWqZEn8=; b=u2QtK0Op/2QPxZ6Pb5EB05Ne+6PGbVGIpPhvQ36h4n0ckI1mgq1uUXvOo/FLSM2JdA fwqts3esJNbcyQ92np4FtLEMTtBN71v6DdHNaKvsN9QuG6B3DXNXQx//Kqj1RPwplEXl w6znbJeQdEUuZ/wkHd/t/Aq9oEwQhAiljPAikswg0ymDPXfsjbkUoJ13W2cb5LdKAoZ0 /J/OCO8ytv/jG46vs/ql9c9Ki69uXtFJlFGJ9i0iFHSAIjYnfn50BgaPncsgD1UtVshB m7jQ/mVMLSATnpa4eGmTGFdS1oZxgsQpyb55+VQQypzk4C5EQVEWUdT+7ViIt6KuNHLX vPEQ== MIME-Version: 1.0 X-Received: by 10.180.198.146 with SMTP id jc18mr8324wic.61.1375394652529; Thu, 01 Aug 2013 15:04:12 -0700 (PDT) Sender: jdcryans@gmail.com Received: by 10.194.139.114 with HTTP; Thu, 1 Aug 2013 15:04:12 -0700 (PDT) In-Reply-To: References: Date: Thu, 1 Aug 2013 15:04:12 -0700 X-Google-Sender-Auth: SF6Q2TY8xeBjMiC-2k-QQpeDwkU Message-ID: Subject: Re: HDFS Restart with Replication From: Jean-Daniel Cryans To: "user@hbase.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org I can't think of a way how your missing blocks would be related to HBase replication, there's something else going on. Are all the datanodes checking back in? J-D On Thu, Aug 1, 2013 at 2:17 PM, Patrick Schless wrote: > I'm running: > CDH4.1.2 > HBase 0.92.1 > Hadoop 2.0.0 > > Is there an issue with restarting a standby cluster with replication > running? I am doing the following on the standby cluster: > > - stop hmaster > - stop name_node > - start name_node > - start hmaster > > When the name node comes back up, it's reliably missing blocks. I started > with 0 missing blocks, and have run through this scenario a few times, and > am up to 46 missing blocks, all from the table that is the standby for our > production table (in a different datacenter). The missing blocks all are > from the same table, and look like: > > blk_-2036986832155369224 /hbase/splitlog/data01.sea01.staging.tdb.com > ,60020,1372703317824_hdfs%3A%2F%2Fname-node.sea01.staging.tdb.com > %3A8020%2Fhbase%2F.logs%2Fdata05.sea01.staging.tdb.com > %2C60020%2C1373557074890-splitting%2Fdata05.sea01.staging.tdb.com > %252C60020%252C1373557074890.1374960698485/tempodb-data/c9cdd64af0bfed70da154c219c69d62d/recovered.edits/0000000001366319450.temp > > Do I have to stop replication before restarting the standby? > > Thanks, > Patrick