[ https://issues.apache.org/jira/browse/HBASE-21444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ankit Singhal updated HBASE-21444: ---------------------------------- Attachment: (was: HBASE-21440.branch-2.0.002.patch) > 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)