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

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

HBASE-21421 is also a problem introduced by this method. So in general, I do 
not think we should actually do anything in this method, instead, just log the 
possible inconsistencies.

> 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
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0
>
>
> 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