[jira] [Updated] (HBASE-24552) Replica region needs to do check if primary region exists in hdfs during createRegionOnFileSystem().

["Huaxiang Sun (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-24552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Huaxiang Sun updated HBASE-24552:
---------------------------------
    Description: 
In hbase-1, it always runs into the situation that primary region has been closed/removed and replica region still stays in master's in-memory db and open at one of the region servers. Balancer can move this replica region to a new region server. During the region open, replica region does not check if primary region has been removed and moves forward. During store open, it will recreates primary region directory at hdfs and caused inconsistency.

 

In hbase-2, things get much better. To prevent the above inconsistency from happening, it adds more checks for a replica region, i.e, if primary regions' directory exists and there is a .regioninfo under. 

  was:
When a replica is opened, it does not check if region dir exists and if .regionInfo exists in the directory, region server will online this replica region even the primary region does not exist. 

 

It needs to do better to do more checks and fails region open if the check does not pass.

Maybe we can do this check in master, will see.

 

 


> Replica region needs to do check if primary region exists in hdfs during createRegionOnFileSystem().
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-24552
>                 URL: https://issues.apache.org/jira/browse/HBASE-24552
>             Project: HBase
>          Issue Type: Bug
>          Components: read replicas
>    Affects Versions: 2.3.0
>            Reporter: Huaxiang Sun
>            Assignee: Huaxiang Sun
>            Priority: Major
>
> In hbase-1, it always runs into the situation that primary region has been closed/removed and replica region still stays in master's in-memory db and open at one of the region servers. Balancer can move this replica region to a new region server. During the region open, replica region does not check if primary region has been removed and moves forward. During store open, it will recreates primary region directory at hdfs and caused inconsistency.
>  
> In hbase-2, things get much better. To prevent the above inconsistency from happening, it adds more checks for a replica region, i.e, if primary regions' directory exists and there is a .regioninfo under. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)