[
https://issues.apache.org/jira/browse/HBASE-9468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762634#comment-13762634
]
Enis Soztutar commented on HBASE-9468:
--------------------------------------
I think we should remove the recovering logic in the master from a zk session
expiration. Failing the master, and letting the backup masters take over and/or
restart by the admin or supervisor is simpler and more bullet proof. The
masterRecovery parameter in HMaster#finishInitialization() complicates things.
> Previous active master can still serves RPC request when it is trying
> recovering expired zk session
> ---------------------------------------------------------------------------------------------------
>
> Key: HBASE-9468
> URL: https://issues.apache.org/jira/browse/HBASE-9468
> Project: HBase
> Issue Type: Bug
> Reporter: Feng Honghua
>
> When the active master's zk session expires, it'll try to recover zk session,
> but without turn off its RpcServer. What if a previous backup master has
> already become the now active master, and some client tries to send request
> to this expired master by using the cached master info? Any problem here?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
