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 2A4C8107C0 for ; Tue, 18 Mar 2014 17:34:33 +0000 (UTC) Received: (qmail 72325 invoked by uid 500); 18 Mar 2014 17:34:28 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 72273 invoked by uid 500); 18 Mar 2014 17:34:26 -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 72264 invoked by uid 99); 18 Mar 2014 17:34:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Mar 2014 17:34:26 +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 theo.bertozzi@gmail.com designates 209.85.213.45 as permitted sender) Received: from [209.85.213.45] (HELO mail-yh0-f45.google.com) (209.85.213.45) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Mar 2014 17:34:21 +0000 Received: by mail-yh0-f45.google.com with SMTP id a41so7277644yho.32 for ; Tue, 18 Mar 2014 10:34:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=tAG8pHdMyarHPt6qeI3fvKRfZMvbDRmV5UC5WoDjRZs=; b=fmO9B58+uLgtRZ9wLWoVXz9/agh3GwZltHcZnVB+m4BXBJl7RJF5Zg17svK6Xm+a35 Gd9oWBFci5IPwya2ZwX2qrf6OJVndlEtTOTEMq1WVGKbsHqB/AKTHUTf6zGVwLhJ1Hwr He9Qq3vGM+/4D/18hJw3c9NKtyoqeOt/D609Bvnht0GuC5+tpgEdCHwCdyg590HNnUKs Pyp1jhUJS44YHYuORdO2KZDBfuQ5XmTQbCYPV1wa4qtuSUAFh4jFcsMpU2SxR/peez9O UnWoM+ndLRX+L+qRyBAm7ay6h1NwlzCpgVCypOpgnz+PgRif0ryd10wdgO4yb8srgGez AIGw== X-Received: by 10.236.102.39 with SMTP id c27mr43803516yhg.26.1395164041186; Tue, 18 Mar 2014 10:34:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.170.76.215 with HTTP; Tue, 18 Mar 2014 10:33:41 -0700 (PDT) In-Reply-To: References: <53287DF001E4042800392A3F_0_66113@p057> From: Matteo Bertozzi Date: Tue, 18 Mar 2014 17:33:41 +0000 Message-ID: Subject: Re: Corrupt HBase table To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=20cf3011d90b14143d04f4e4f1ea X-Virus-Checked: Checked by ClamAV on apache.org --20cf3011d90b14143d04f4e4f1ea Content-Type: text/plain; charset=ISO-8859-1 can you try to read the file by using: org.apache.hadoop.hbase.io.hfile.HFile -f FILE_PATH -s -e to verify if the problem is reading the block from cache or the data on disk is corrupted in some way? The stacktrace is showing a file size > 255GB and a Key of 16M which I doubt being correct. Matteo On Tue, Mar 18, 2014 at 5:26 PM, Ted Yu wrote: > The stack trace doesn't reveal too much other than the error occurred at > the beginning of a scan. > > Other experts would have more insights than I do. > > Cheers > > > On Tue, Mar 18, 2014 at 10:10 AM, Sudarshan Kadambi (BLOOMBERG/ 731 LEXIN) > < > skadambi@bloomberg.net> wrote: > > > Thanks Ted. No, we don't use data block encoding. This is 0.96. It > appears > > multiple HFiles are affected. Does the stack trace give some context on > > what is that it's attempting to do at the lowest level? > > > > > > ----- Original Message ----- > > From: yuzhihong@gmail.com > > To: Sudarshan Kadambi (BLOOMBERG/ 731 LEXIN) , > > user@hbase.apache.org > > At: Mar 18 2014 13:03:20 > > > > Are you using Data Block Encoding for this table ? > > > > Can you sideline the HFile and see if other HFiles were affected ? > > > > I assume you use 0.94.x > > > > Cheers > > > > > > On Tue, Mar 18, 2014 at 7:14 AM, Sudarshan Kadambi (BLOOMBERG/ 731 LEXIN) > > wrote: > > > >> Hi Folks: > >> > >> We've a table that we're unable to make online. A scan on this table > >> yields the following stack trace. hbck doesn't report any > inconsistencies. > >> I went ahead and did a repair, which didn't make a difference. Any tips? > >> > >> ERROR: java.io.IOException: Invalid currKeyLen 16777280 or currValueLen > >> 64. Block offset: 274609471488, block length: 16415, position: 0 > (without > >> header). > >> at > org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2213) > >> at > >> org.apache.hadoop.hbase.ipc.RpcServer$Handler.run(RpcServer.java:1879) > >> Caused by: java.lang.IllegalStateException: Invalid currKeyLen 16777280 > >> or currValueLen 64. Block offset: 274609471488, block length: 16415, > >> position: 0 (without header). > >> at > >> > org.apache.hadoop.hbase.io.hfile.HFileReaderV2$ScannerV2.readKeyValueLen(HFileReaderV2.java:820) > >> at > >> > org.apache.hadoop.hbase.io.hfile.HFileReaderV2$ScannerV2.updateCurrBlock(HFileReaderV2.java:787) > >> at > >> > org.apache.hadoop.hbase.io.hfile.HFileReaderV2$ScannerV2.seekTo(HFileReaderV2.java:749) > >> at > >> > org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:232) > >> at > >> > org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:145) > >> at > >> > org.apache.hadoop.hbase.regionserver.StoreScanner.(StoreScanner.java:168) > >> at > >> org.apache.hadoop.hbase.regionserver.HStore.getScanner(HStore.java:1642) > >> at > >> > org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.(HRegion.java:3460) > >> at > >> > org.apache.hadoop.hbase.regionserver.HRegion.instantiateRegionScanner(HRegion.java:1768) > >> at > >> > org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1760) > >> at > >> > org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1737) > >> at > >> > org.apache.hadoop.hbase.regionserver.HRegionServer.scan(HRegionServer.java:2996) > >> at > >> > org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:26929) > >> at > org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2175) > >> ... 1 more > >> > >> > > > --20cf3011d90b14143d04f4e4f1ea--