You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Pankaj Kumar (Jira)" <ji...@apache.org> on 2021/04/01 11:30:00 UTC
[jira] [Updated] (HBASE-25717) RegionServer aborted due to
ClassCastException
[ https://issues.apache.org/jira/browse/HBASE-25717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pankaj Kumar updated HBASE-25717:
---------------------------------
Summary: RegionServer aborted due to ClassCastException (was: RegionServer aborted with due to ClassCastException)
> RegionServer aborted due to ClassCastException
> ----------------------------------------------
>
> Key: HBASE-25717
> URL: https://issues.apache.org/jira/browse/HBASE-25717
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.2.6, 2.3.4, 2.4.2
> Reporter: chiranjeevi
> Assignee: Pankaj Kumar
> Priority: Major
> Fix For: 3.0.0-alpha-1
>
>
> {color:#000000}Observed RegionServer crash while writing huge data concurrently through YCSB tool,
> {noformat}
> 2021-03-29 14:35:37,860 | ERROR | RpcServer.priority.RWQ.Fifo.write.handler=19,queue=3,port=RS_PORT | ***** ABORTING region server RS_IP,RS_PORT,1616999325078: The coprocessor org.apache.hadoop.hbase.coprocessor.MetaTableMetrics threw java.lang.ClassCastException: java.util.HashMap$Node cannot be cast to java.util.HashMap$TreeNode ***** | org.slf4j.helpers.MarkerIgnoringBase.error(MarkerIgnoringBase.java:159)
> java.lang.ClassCastException: java.util.HashMap$Node cannot be cast to java.util.HashMap$TreeNode
> at java.util.HashMap$TreeNode.moveRootToFront(HashMap.java:1835)
> at java.util.HashMap$TreeNode.treeify(HashMap.java:1951)
> at java.util.HashMap.treeifyBin(HashMap.java:772)
> at java.util.HashMap.putVal(HashMap.java:644)
> at java.util.HashMap.put(HashMap.java:612)
> at java.util.HashSet.add(HashSet.java:220)
> at org.apache.hadoop.hbase.coprocessor.MetaTableMetrics$ExampleRegionObserverMeta.registerAndMarkMeter(MetaTableMetrics.java:200)
> at org.apache.hadoop.hbase.coprocessor.MetaTableMetrics$ExampleRegionObserverMeta.regionMetricRegisterAndMark(MetaTableMetrics.java:173)
> at org.apache.hadoop.hbase.coprocessor.MetaTableMetrics$ExampleRegionObserverMeta.registerAndMarkMetrics(MetaTableMetrics.java:106)
> at org.apache.hadoop.hbase.coprocessor.MetaTableMetrics$ExampleRegionObserverMeta.prePut(MetaTableMetrics.java:91)
> at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$23.call(RegionCoprocessorHost.java:948)
> at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost$23.call(RegionCoprocessorHost.java:945)
> at org.apache.hadoop.hbase.coprocessor.CoprocessorHost$ObserverOperationWithoutResult.callObserver(CoprocessorHost.java:581)
> at org.apache.hadoop.hbase.coprocessor.CoprocessorHost.execOperation(CoprocessorHost.java:655)
> at org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.prePut(RegionCoprocessorHost.java:945)
> {noformat}
> This problem occured only once in my test cluster. Discussed offline with [~pankajkumar] it looks like race condition in MetaTableMetrics.metrics.{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)