Hello, I prepared two patched that allowed me to resolve this issue by deploying it on an RS that hosts the hbase:meta table. You can find more details in the following two upstream issues I have opened with additional patches used for resolving the issue: https://issues.apache.org/jira/browse/HBASE-29633 https://issues.apache.org/jira/browse/HBASE-29554 From my investigation this problem was not solvable without the extra patches. I have tested and fixed it in HBase v2.5.10 succesfully. ... View more

Just to add even more input on this, I can see a side effect of it shown in the HBCK report under Inconsistent Regions  Just to add more input on this, in the HBase master logs I can also see: <2025-09-16T10:11:27.734+0200> <WARN> <janitor.ReportMakingVisitor>: <INCONSISTENCY: Row name is not equal to serialized info:regioninfo content; row=XXX:XXX,e14ef354e1644a6a2b229ffde05f38d3 XXX:XXX,test,12345.07a983faf71bc641bfbb4e8736d378ac.; See if RegionInfo is referenced in another hbase:meta row? Delete?> In meta: XXX:XXX,e14ef354e1644a6a2b229ffde05f38d3 column=info:regioninfo, timestamp=2025-08-26T12:12:21.389, value={ENCODED => 07a983faf71bc641bfbb4e8736d378ac, NAME => 'XXX:XXX,test,12345.07a983faf71bc641bfbb4e8736d378ac.', STARTKEY => 'test', ENDKEY => ''}      ... View more

@DianaTorres thank you for your prompt reply. I haven't found a solution to this problem as of now. If you have any suggestions on how to solve this issue and get rid of the corrupted meta entries in the existing cluster, I would highly appreciate it. Thank you in advance. ... View more