[
https://issues.apache.org/jira/browse/HBASE-29579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18018890#comment-18018890
]
Andor Molnar commented on HBASE-29579:
--------------------------------------
It's not related to {*}HbckChore{*}.
*FSTableDescriptors* scans the filesystem at startup and caches the list of
tablenames which is being returned in the _getAll()_ method. I think we should
add a list of dirs to be excluded.
> AssignmentManager is trying to pick up the other cluster's meta table after
> HbckChore run
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-29579
> URL: https://issues.apache.org/jira/browse/HBASE-29579
> Project: HBase
> Issue Type: Sub-task
> Reporter: Andor Molnar
> Priority: Major
>
> I see this on both clusters. *AssignmentManager* runs into the following
> issue:
> {noformat}
> 2025-09-08T16:34:25,004 INFO [master/hbase-docker:16000.Chore.1]
> hbck.HbckChore: Loaded 2 regions (0 disabled, 0 split parents) from in-memory
> state
> 2025-09-08T16:34:25,005 INFO [master/hbase-docker:16000.Chore.1]
> hbck.HbckChore: Loaded 2 regions from 1 regionservers' reports and found 0
> orphan regions
> 2025-09-08T16:34:25,013 INFO [master/hbase-docker:16000.Chore.1]
> hbck.HbckChore: Loaded 3 tables 3 regions from filesystem and found 1 orphan
> regions
> 2025-09-08T16:35:24,183 ERROR [master/hbase-docker:16000.Chore.1]
> master.TableStateManager: Unable to get table hbase:meta_replica1 state
> org.apache.hadoop.hbase.TableNotFoundException: No state found for
> hbase:meta_replica1
> at
> org.apache.hadoop.hbase.master.TableStateManager.getTableState(TableStateManager.java:141)
> ~[hbase-server-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.master.TableStateManager.isTableState(TableStateManager.java:79)
> ~[hbase-server-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.master.assignment.AssignmentManager.isTableDisabled(AssignmentManager.java:549)
> ~[hbase-server-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.master.assignment.AssignmentManager.getRegionStatesCount(AssignmentManager.java:2637)
> ~[hbase-server-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.master.HMaster.getClusterMetricsWithoutCoprocessor(HMaster.java:3112)
> ~[hbase-server-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.master.HMaster.getClusterMetricsWithoutCoprocessor(HMaster.java:3006)
> ~[hbase-server-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.master.balancer.ClusterStatusChore.chore(ClusterStatusChore.java:47)
> ~[hbase-server-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.ScheduledChore.run(ScheduledChore.java:161)
> ~[hbase-common-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.trace.TraceUtil.lambda$tracedRunnable$2(TraceUtil.java:155)
> ~[hbase-common-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
> ~[?:?]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> ~[?:?]
> at
> org.apache.hadoop.hbase.JitterScheduledThreadPoolExecutorImpl$JitteredRunnableScheduledFuture.run(JitterScheduledThreadPoolExecutorImpl.java:107)
> ~[hbase-common-4.0.0-alpha-1>
> 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) ~[?:?]
> {noformat}
> And the same on the replica cluster:
> {noformat}
> 2025-09-08T16:34:30,442 INFO [master/hbase-docker-2:16000.Chore.1]
> hbck.HbckChore: Loaded 2 regions (0 disabled, 0 split parents) from in-memory
> state
> 2025-09-08T16:34:30,442 INFO [master/hbase-docker-2:16000.Chore.1]
> hbck.HbckChore: Loaded 2 regions from 1 regionservers' reports and found 0
> orphan regions
> 2025-09-08T16:34:30,449 INFO [master/hbase-docker-2:16000.Chore.1]
> hbck.HbckChore: Loaded 3 tables 3 regions from filesystem and found 1 orphan
> regions
> 2025-09-08T16:35:30,546 ERROR [master/hbase-docker-2:16000.Chore.1]
> master.TableStateManager: Unable to get table hbase:meta state
> org.apache.hadoop.hbase.TableNotFoundException: No state found for hbase:meta
> at
> org.apache.hadoop.hbase.master.TableStateManager.getTableState(TableStateManager.java:141)
> ~[hbase-server-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.master.TableStateManager.isTableState(TableStateManager.java:79)
> ~[hbase-server-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.master.assignment.AssignmentManager.isTableDisabled(AssignmentManager.java:549)
> ~[hbase-server-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.master.assignment.AssignmentManager.getRegionStatesCount(AssignmentManager.java:2637)
> ~[hbase-server-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.master.HMaster.getClusterMetricsWithoutCoprocessor(HMaster.java:3112)
> ~[hbase-server-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.master.HMaster.getClusterMetricsWithoutCoprocessor(HMaster.java:3006)
> ~[hbase-server-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.master.balancer.ClusterStatusChore.chore(ClusterStatusChore.java:47)
> ~[hbase-server-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.ScheduledChore.run(ScheduledChore.java:161)
> ~[hbase-common-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> org.apache.hadoop.hbase.trace.TraceUtil.lambda$tracedRunnable$2(TraceUtil.java:155)
> ~[hbase-common-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-SNAPSHOT]
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
> ~[?:?]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
> ~[?:?]
> at
> org.apache.hadoop.hbase.JitterScheduledThreadPoolExecutorImpl$JitteredRunnableScheduledFuture.run(JitterScheduledThreadPoolExecutorImpl.java:107)
> ~[hbase-common-4.0.0-alpha-1-SNAPSHOT.jar:4.0.0-alpha-1-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) ~[?:?]
> {noformat}
> Please check.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
