[jira] [Commented] (HBASE-27181) Change HBCK2's setRegionState() to use HBCK's setRegionStateInMeta()

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

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

Huaxiang Sun commented on HBASE-27181:
--------------------------------------

Instead of current implementation's writing to meta table directly, changed to use HBCK's setRegionStateInMeta(). There are couple advantages, one of them  is that HBCK's setRegionStateInMeta() will set Master's region state besides setting the state in meta table, this will save one active master switchover to bring the in-memory state to be consistent with the region state in meta.

> Change HBCK2's setRegionState() to use HBCK's setRegionStateInMeta()
> --------------------------------------------------------------------
>
>                 Key: HBASE-27181
>                 URL: https://issues.apache.org/jira/browse/HBASE-27181
>             Project: HBase
>          Issue Type: Improvement
>          Components: hbck2
>    Affects Versions: 2.4.13
>            Reporter: Huaxiang Sun
>            Assignee: Huaxiang Sun
>            Priority: Minor
>
> Replica region id is  not recognized by hbck2's setRegionState as it does not show up in meta. We run into cases that it needs to set region state in meta for replica regions in order to fix inconsistency. We ended up writing the state manually into meta table and did a master failover to sync state from meta table. 
>  
> hbck2's setRegionState needs to support replica region id and handles it nicely.
> Currently, setRegionState does not use MasterRpcServices#setRegionStateInMeta. There is an issue in setRegionStateInMeta to support replica regions. After that is fixed, and setRegionState uses setRegionStateInMeta to set the region state, it will support replica Id.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)