[
https://issues.apache.org/jira/browse/HBASE-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16682854#comment-16682854
]
Allan Yang commented on HBASE-21463:
------------------------------------
I think we need the reportTransition call inside checkOnlineRegionsReport.
Since:
1. The master scheduled a AP(TRSP in branch-2+) to RS
2. The RS opened the RS and report to Master successfully.
3. The Master restarts and the AP schedule the open requests again, but since
the RS already opened the region, it ignore the request
4. Then the AP stuck
Another solution is that we can't ignore the open requests even if the region
is already online, we need to send the report request back to master.
> The checkOnlineRegionsReport can accidentally complete a TRSP
> -------------------------------------------------------------
>
> Key: HBASE-21463
> URL: https://issues.apache.org/jira/browse/HBASE-21463
> Project: HBase
> Issue Type: Sub-task
> Components: amv2
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Critical
> Fix For: 3.0.0, 2.2.0
>
> Attachments: HBASE-21463-UT.patch, HBASE-21463-v1.patch,
> HBASE-21463.patch
>
>
> On our testing cluster, we observe a race condition:
> 1. A regionServerReport request is built
> 2. A TRSP is scheduled to reopen the region
> 3. The region is closed at RS side
> 4. The OpenRegionProcedure is created
> 5. The regionServerReport generated at step 1 is executed, and we find that
> the region is opened on the RS, so we update the region state to OPEN.
> 6. The OpenRegionProcedure notices that the region has already been in the
> OPEN state so gives up and finishes.
> 7. The TRSP finishes.
> 8. The region is recorded as OPEN on the RS but actually not, and can not
> recover unless we use HBCK2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)