You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andor Molnar (Jira)" <ji...@apache.org> on 2025/09/08 16:53:00 UTC
[jira] [Created] (HBASE-29580) Clean-up hardcoded meta table names from log entries
Andor Molnar created HBASE-29580:
------------------------------------
Summary: Clean-up hardcoded meta table names from log entries
Key: HBASE-29580
URL: https://issues.apache.org/jira/browse/HBASE-29580
Project: HBase
Issue Type: Sub-task
Reporter: Andor Molnar
During my testing I've found that meta table name is hardcoded in some log entries which is wrong and misleading.
{noformat}
2025-09-08T15:34:29,213 INFO [PEWorker-3] assignment.RegionStateStore: pid=5 updating hbase:meta row=521517121, regionState=OPENING, regionLocation=hbase-docker-2,16020,1757345656415
2025-09-08T15:34:29,218 INFO [PEWorker-3] zookeeper.MetaTableLocator: Setting hbase:meta replicaId=0 location in ZooKeeper as hbase-docker-2,16020,1757345656415, state=OPENING
2025-09-08T15:34:29,558 INFO [PEWorker-5] assignment.RegionStateStore: pid=5 updating hbase:meta row=521517121, regionState=OPEN, openSeqNum=7, regionLocation=hbase-docker-2,16020,1757345656415
2025-09-08T15:34:29,560 INFO [PEWorker-5] zookeeper.MetaTableLocator: Setting hbase:meta replicaId=0 location in ZooKeeper as hbase-docker-2,16020,1757345656415, state=OPEN
{noformat}
We should see *hbase:meta_replica1* everywhere in the logs. Please find and fix them.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)