[ 
https://issues.apache.org/jira/browse/HBASE-21463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16682857#comment-16682857
 ] 

Duo Zhang commented on HBASE-21463:
-----------------------------------

So on branch-2.1 and branch-2.0 the AP will schedule the open request again? 
For TRSP it won't schedule the open request again as in the 
reportRegionStateTransition method we will finish the TRSP, so if the 
reportRegionStateTransition is succeeded, then we are done.

> 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)

Reply via email to