Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 6 Jun 2017 04:03:18 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13071045.1494477061000.524.1496721798342@Atlassian.JIRA>
In-Reply-To: <JIRA.13071045.1494477061000@Atlassian.JIRA>
References: <JIRA.13071045.1494477061000@Atlassian.JIRA> <JIRA.13071045.1494477061821@jira-lw-us.apache.org>
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
archived-at: Tue, 06 Jun 2017 04:03:24 -0000


    [ https://issues.apache.org/jira/browse/HBASE-18030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038077#comment-16038077 ] 

ramkrishna.s.vasudevan commented on HBASE-18030:
------------------------------------------------

bq.The visibility and ACL tags already handle this possible duplicated tags issue (With increments/Append)
If already handled it is fine. 
Just asking - Should we unify the way the tag removal happens for all the cases (and future cases that are possible)?
+1.

> 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.<init>(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)