[ https://issues.apache.org/jira/browse/HBASE-21444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677687#comment-16677687 ]
Ankit Singhal commented on HBASE-21444: --------------------------------------- bq. The patch can't apply to branch-2.0, can you rebase? Uploaded a rebased patch. bq. This may be similar with HBASE-21035, you can refer to some discussions there. Yeah, this looks very similar, it seems we don't have a conclusion on the approach yet. so what are the next steps? I think it is important that assignment of meta and namespace should get automatically be recovered(either through a restart or by monitor thread) so that user has at least master initialized to carry out any other operation needed to resolve other user region assignments issues. > Recover meta in case of long ago dead region server appear in meta znode > ------------------------------------------------------------------------ > > Key: HBASE-21444 > URL: https://issues.apache.org/jira/browse/HBASE-21444 > Project: HBase > Issue Type: Bug > Affects Versions: 2.0.2 > Reporter: Ankit Singhal > Assignee: Ankit Singhal > Priority: Major > Attachments: HBASE-21444.branch-2.0.001.patch, > HBASE-21444.branch-2.0.002.patch > > > Ambari metric server uses HBase as storage and currently have different > znodes (/hbase-unsecure and /hbase-secure) to differentiate secure/unsecure > deployment of HBase. > As it also supports the rollback of the cluster from kerberised to > non-kerberised (includes step of changing znode from /hbase-secure to > /hbase-unsecure) , but with HBase 2.0 , meta-region-server znode from old > zookeeper znodes will have regionserver which was long ago gone and there > will be no procedure to transition it, resulting it to get stuck for lifetime. > One option is to clear the znodes before rollingback but as it used to work > with prior releases due to RecoverMetaProcedure, the ask is if we can fix > meta assignment in case the wrong state is available in znode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)