[ https://issues.apache.org/jira/browse/HBASE-23313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125566#comment-17125566 ]
Duo Zhang commented on HBASE-23313: ----------------------------------- For RegionInfo, the regionName and encodedName should be generated according to other fields, so passing it through the proto message is not necessary. I think encoded name is used elsewhere, for example, in RegionSpecifier? As a region name and a encoded region name can both be used as an identifier of a region. For me, I suggest we just remove the field, since it has not been published yet. Thanks. > [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)