Duo Zhang created HBASE-29188:
---------------------------------
Summary: Region replica replication can not handle table drop
correctly
Key: HBASE-29188
URL: https://issues.apache.org/jira/browse/HBASE-29188
Project: HBase
Issue Type: Bug
Components: read replicas
Reporter: Duo Zhang
After the rolling upgrading test, I disabled and then dropped the table, all
region servers finally aborted because of
{noformat}
2025-03-15T02:16:51,266 ERROR
[RS_REGION_REPLICA_FLUSH_OPS-regionserver/data01:16020-1]
regionserver.HRegionServer: ***** ABORTING region server
data01,16020,1742003804245: ServerAborting because an exception was thrown *****
org.apache.hadoop.hbase.TableNotFoundException: test_ns:test_tn
at java.lang.Thread.getStackTrace(Thread.java:1619) ~[?:?]
at
org.apache.hadoop.hbase.util.FutureUtils.setStackTrace(FutureUtils.java:144)
~[hbase-common-3.0.0-beta-2-SNAPSHOT.jar:3.0.0-beta-2-SNAPSHOT]
at
org.apache.hadoop.hbase.util.FutureUtils.rethrow(FutureUtils.java:163)
~[hbase-common-3.0.0-beta-2-SNAPSHOT.jar:3.0.0-beta-2-SNAPSHOT]
at org.apache.hadoop.hbase.util.FutureUtils.get(FutureUtils.java:186)
~[hbase-common-3.0.0-beta-2-SNAPSHOT.jar:3.0.0-beta-2-SNAPSHOT]
at
org.apache.hadoop.hbase.regionserver.handler.RegionReplicaFlushHandler.triggerFlushInPrimaryRegion(RegionReplicaFlushHandler.java:119)
~[hbase-server-3.0.0-beta-2-SNAPSHOT.jar:3.0.0-beta-2-SNAPSHOT]
at
org.apache.hadoop.hbase.regionserver.handler.RegionReplicaFlushHandler.process(RegionReplicaFlushHandler.java:66)
~[hbase-server-3.0.0-beta-2-SNAPSHOT.jar:3.0.0-beta-2-SNAPSHOT]
at
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:104)
~[hbase-server-3.0.0-beta-2-SNAPSHOT.jar:3.0.0-beta-2-SNAPSHOT]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
~[?:?]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
~[?:?]
at java.lang.Thread.run(Thread.java:840) ~[?:?]
at --------Future.get--------(Unknown Source) ~[?:?]
{noformat}
We need to handle the table dropping correctly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
