hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18030) Per Cell TTL tags may get duplicated with increments/Append causing tags length overflow
Date Tue, 06 Jun 2017 04:39:18 GMT

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

Anoop Sam John commented on HBASE-18030:
----------------------------------------

You mean remove duplicate Tag types?  May be not. As such we dont have any restriction like
there should not be duplicated tags in a Cell. So it depends on the Tag type.. I tried to
make it like unique Tag types in a Cell way.  But then gave up with above thinking.  As of
now this way is ok.  When we allow custom tags also, lets think.
Will commit this.
This has to be committed to branch-1, branch-1.3, branch-1.2 at least.

> 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)

Mime
View raw message