Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 5C971200C7C for ; Mon, 5 Jun 2017 19:27:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5B621160BBB; Mon, 5 Jun 2017 17:27:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A6F24160BD4 for ; Mon, 5 Jun 2017 19:27:08 +0200 (CEST) Received: (qmail 24062 invoked by uid 500); 5 Jun 2017 17:27:07 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 24051 invoked by uid 99); 5 Jun 2017 17:27:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Jun 2017 17:27:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 481D0C061B for ; Mon, 5 Jun 2017 17:27:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id DrqCDd762fKm for ; Mon, 5 Jun 2017 17:27:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 19D2C5FBC5 for ; Mon, 5 Jun 2017 17:27:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 46651E0BCA for ; Mon, 5 Jun 2017 17:27:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 6009421B59 for ; Mon, 5 Jun 2017 17:27:04 +0000 (UTC) Date: Mon, 5 Jun 2017 17:27:04 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-18030) Per Cell TTL tags may get duplicated with increments/Append causing tags length overflow MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 05 Jun 2017 17:27:09 -0000 [ https://issues.apache.org/jira/browse/HBASE-18030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16037247#comment-16037247 ] Ted Yu commented on HBASE-18030: -------------------------------- lgtm > Per Cell TTL tags may get duplicated with increments/Append causing tags length overflow > ---------------------------------------------------------------------------------------- > > Key: HBASE-18030 > URL: https://issues.apache.org/jira/browse/HBASE-18030 > Project: HBase > Issue Type: Bug > Components: hbase, regionserver > Affects Versions: 1.0.0, 2.0.0, 0.98.9 > Reporter: Abhishek Kumar > Assignee: Anoop Sam John > Priority: Critical > Attachments: HBASE-18030_initial.patch, HBASE-18030.patch > > > 2017-04-29 14:24:14,135 ERROR [B.fifo.QRpcServer.handler=49,queue=1,port=16020] ipc.RpcServer: Unexpected throwable object java.lang.IllegalStateException: Invalid currTagsLen -32712. Block offset: 3707853, block length: 72841, position: 0 (without header). at org.apache.hadoop.hbase.io.hfile.HFileReaderV3$ScannerV3.checkTagsLen(HFileReaderV3.java:226) > I am not not using any hbase tags feature. > The Increment operation from the application side is triggering this error. The same is happening when scanner is run on this table. It feels that one or more particular HFile block is corrupt (with negative tagLength). > hbase(main):007:0> scan 'table-name', {LIMIT=>1,STARTROW=>'ad:event_count:a'} > Returning the result > hbase(main):008:0> scan 'table-name', {LIMIT=>1,STARTROW=>'ad:event_count:b'} > ROW COLUMN+CELL > ERROR: java.io.IOException: java.lang.IllegalStateException: Invalid currTagsLen -32701. Block offset: 272031, block length: 72441, position: 32487 (without header). > at org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.handleException(HRegion.java:5607) > at org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.(HRegion.java:5579) > at org.apache.hadoop.hbase.regionserver.HRegion.instantiateRegionScanner(HRegion.java:2627) > at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2613) > at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:2595) > at org.apache.hadoop.hbase.regionserver.RSRpcServices.scan(RSRpcServices.java:2282) > at org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:32295) -- This message was sent by Atlassian JIRA (v6.3.15#6346)