liangxiaodong created HBASE-24484:
-------------------------------------

             Summary: Scanners for Replicas region return many HFileLink name 
exceptions
                 Key: HBASE-24484
                 URL: https://issues.apache.org/jira/browse/HBASE-24484
             Project: HBase
          Issue Type: Bug
          Components: read replicas
    Affects Versions: 2.2.4
            Reporter: liangxiaodong


When region read replicas is enabled and scan is running, regionsevers logged 
so many warns as follows;It appears replicas region StoreFileInfo took normal 
hfile as filelink , however function getActiveFileName would throw exception 
when checking filelink format.

2020-05-31 10:40:48,486 WARN 
[RpcServer.default.RWQ.Fifo.scan.handler=238,queue=238,port=16020] 
regionserver.StoreScanner: failed to switch to stream read 
java.lang.IllegalArgumentException: 153052181a084e70a1242870fe6e4961 is not a 
valid HFileLink name! 
 at 
org.apache.hadoop.hbase.io.HFileLink.getReferencedHFileName(HFileLink.java:252) 
 at 
org.apache.hadoop.hbase.regionserver.StoreFileInfo.getActiveFileName(StoreFileInfo.java:624)
 
 at 
org.apache.hadoop.hbase.regionserver.HStore.recreateScanners(HStore.java:2104) 
 at 
org.apache.hadoop.hbase.regionserver.StoreScanner.trySwitchToStreamRead(StoreScanner.java:1068)
 
 at 
org.apache.hadoop.hbase.regionserver.StoreScanner.shipped(StoreScanner.java:1202)
 
 at 
org.apache.hadoop.hbase.regionserver.KeyValueHeap.shipped(KeyValueHeap.java:437)
 
 at 
org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.shipped(HRegion.java:7037)
 
 at 
org.apache.hadoop.hbase.regionserver.RSRpcServices$RegionScannerShippedCallBack.run(RSRpcServices.java:396)
 
 at org.apache.hadoop.hbase.ipc.ServerCall.setResponse(ServerCall.java:289) 
 at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:167) 
 at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:338) 
 at org.apache.hadoop.hbase.ipc.RpcExecutor$Handler.run(RpcExecutor.java:318)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to