[
https://issues.apache.org/jira/browse/HBASE-9468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762964#comment-13762964
]
stack commented on HBASE-9468:
------------------------------
How hard [~fenghh] to make it so we take down rpc during recovery attempt? If
recovery succeeds put the rpc backup again? (I believe you suggested this
even). I am thinking about the non-sophisticated user running on a small
cluster probably without a backup master. In this case, they'd prefer their
master keep running if at all possible, if it recovers its zk session.
If it complicates or muddles your patch or if the gap between zk getting the
callback and being able to shutdown rpc is too large, lets not bother. Just
thought I'd ask.
> 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
