[jira] [Comment Edited] (HBASE-23313) [hbck2] setRegionState should update Master in-memory state too

["Michael Stack (Jira)" <ji...@apache.org>]

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

Michael Stack edited comment on HBASE-23313 at 6/4/20, 4:36 AM:
----------------------------------------------------------------

I made remark in PR on this new field. Thought it interesting it wasn't there already. Didn't realize it not used. You thinking it shouldn't be there; that it should be calculated on deserialization rather than carried in pb? Maybe that is what we do regardless of this addition?


was (Author: stack):
I made remark in PR on this new field. Thought it interesting it wasn't there already. Didn't realize it not used. You thinking it shouldn't be there; that it should be calculated on deserialization rather than carried in pb?

> [hbck2] setRegionState should update Master in-memory state too
> ---------------------------------------------------------------
>
>                 Key: HBASE-23313
>                 URL: https://issues.apache.org/jira/browse/HBASE-23313
>             Project: HBase
>          Issue Type: Bug
>          Components: hbck2
>    Affects Versions: 2.1.7, 2.2.2
>            Reporter: Michael Stack
>            Assignee: Wellington Chevreuil
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.3.0
>
>
> setRegionState changes the hbase:meta table info:state column. It does not alter the Master's in-memory state. This means you have to kill Master and have another assume Active Master role of a state-change to be noticed. Better if the setRegionState just went via Master and updated Master and hbase:meta.



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