You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/16 18:31:00 UTC
[jira] [Resolved] (HBASE-9932) Remove Master Recovery handling when ZK session expired
[ https://issues.apache.org/jira/browse/HBASE-9932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell resolved HBASE-9932.
----------------------------------------
Resolution: Not A Problem
> Remove Master Recovery handling when ZK session expired
> -------------------------------------------------------
>
> Key: HBASE-9932
> URL: https://issues.apache.org/jira/browse/HBASE-9932
> Project: HBase
> Issue Type: Brainstorming
> Reporter: Jeffrey Zhong
> Priority: Major
>
> Currently we use HMaster#tryRecoveringExpiredZKSession to allow master recovery from a ZK session expired error. While this triggers to initialize HMaster partially, it is error prone because it's hard to guarantee the half initialized master is in correct state. I found several times already that the registered ZK listeners are different before & after a fail over.
> Since we already have HA support, I'm proposing to remove this part handling. Though we have a configuration setting "fail.fast.expired.active.master" to skip the logic, why not go one stop further to clean the master code.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)