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 B40EE9004 for ; Tue, 3 Jul 2012 05:55:35 +0000 (UTC) Received: (qmail 90323 invoked by uid 500); 3 Jul 2012 05:55:34 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 90047 invoked by uid 500); 3 Jul 2012 05:55:33 -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 90019 invoked by uid 99); 3 Jul 2012 05:55:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jul 2012 05:55:32 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of eorstvz@gmail.com designates 74.125.82.169 as permitted sender) Received: from [74.125.82.169] (HELO mail-we0-f169.google.com) (74.125.82.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jul 2012 05:55:27 +0000 Received: by wefh52 with SMTP id h52so5363070wef.14 for ; Mon, 02 Jul 2012 22:55:06 -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=EajAuTCqHpkALm+DgjB9AhQG2FuL8Wxd0SfW3kY611w=; b=qr8cBWev1T4uy/5afCsKJ9COk1mWt4I9jz/mpNbvn8fiRFsyrCyGq68FGKRaUBhn8H abMe60GEBr4FcEF78mdInjDU2JvMWrrENEaB1gurexsMKPdrRIGkDQ58rR2UpH4zRbTn MWQLqpJYq2pzj3QL3djl65b5gvvAJYFCWDU/PPNgkLX1zyeGu/osRNpMnO/mJ8iA+XFC dlsKABm6WHa52i1PryyRaSsO8+odBIkCmFZKfIbw5E18xnfF//kl80D7R5p36kJW34Ii qhwnWeZUh+iQJrG0hQ7TsHRLiAwq78XQx8dsxjHH21Y3R+fDN5VlyNkJ+PXov6NE52dD 7CbA== MIME-Version: 1.0 Received: by 10.180.100.133 with SMTP id ey5mr22266920wib.4.1341294906687; Mon, 02 Jul 2012 22:55:06 -0700 (PDT) Received: by 10.216.32.69 with HTTP; Mon, 2 Jul 2012 22:55:06 -0700 (PDT) In-Reply-To: References: Date: Tue, 3 Jul 2012 11:25:06 +0530 Message-ID: Subject: Re: WAL corruption From: manoj p To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=f46d0444ee2773bffb04c3e68e9c --f46d0444ee2773bffb04c3e68e9c Content-Type: text/plain; charset=ISO-8859-1 Hi bryan, WAL is used only during minor compaction. During major compaction WAL is not used. Cheers, Manoj.P On Mon, Jul 2, 2012 at 11:00 PM, Bryan Keller wrote: > During an upgrade of my cluster to 0.90 to 0.92 over the weekend, the WAL > (files in the /hbase/.logs directory) was corrupted and it prevented HBase > from starting up. The exact exception was "java.io.IOException: Could not > obtain the last block locations" on the WAL files. > > I was able to recover by deleting the /hbase/.logs directory. My question > is, if HBase had no pending updates, i.e. nothing writing to it, is there > any risk of data loss by deleting the WAL directory? For example, does > rebalancing, flushing, or compaction use the WAL or is the WAL used only > for inserts/updates/deletes? > > --f46d0444ee2773bffb04c3e68e9c--