[
https://issues.apache.org/jira/browse/HBASE-26864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Huaxiang Sun updated HBASE-26864:
---------------------------------
Description:
Changed the issue title and description for the scope of the work.
The reason
was:
For some upgrading cases, we found that master issues RegionOpen for an already
open region and Region Sever simply logs
{code:java}
2022-03-17 22:16:55,595 WARN
org.apache.hadoop.hbase.regionserver.handler.AssignRegionHandler: Received OPEN
for
foo,b2875fcb-7bc0-4fa9-a980-e902faf7f151,1631771037620.def199cc7208615b783b285f582ddfa4.
which is already online {code}
and it does not ack or nack master. This OpenRegionProceduce is stuck forever.
In this specific case, it needs to ack master that region is open.
For the cause of why it sent an OpenRegion request for an already open region,
it will be followed by another issue.
> SplitTableRegionProcedure, it calls openParentRegions() at a wrong state
> during rollback.
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-26864
> URL: https://issues.apache.org/jira/browse/HBASE-26864
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
> Affects Versions: 2.4.10
> Reporter: Huaxiang Sun
> Assignee: Huaxiang Sun
> Priority: Major
>
> Changed the issue title and description for the scope of the work.
> The reason
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
