[
https://issues.apache.org/jira/browse/HBASE-9468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-9468:
-------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed 0.96 and trunk. Thanks for the patch [~fenghh].
I added the below to the refguide too as part of this commit:
{code}
+ <section xml:id="backup.master.fail.fast"><title>If a backup Master,
making primary Master fail fast</title>
+ <para>If the primary Master loses its connection with ZooKeeper, it
will fall into a loop where it
+ keeps trying to reconnect. Disable this functionality if you
are running more than one Master:
+ i.e. a backup Master. Failing to do so, the dying Master may
continue to receive RPCs though
+ another Master has assumed the role of primary.
+ See the configuration <xref
linkend="fail.fast.expired.active.master" />.
+
+ </para>
</section>
+ </section>
{code}
> 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
> Assignee: Feng Honghua
> Fix For: 0.98.0, 0.96.0
>
> Attachments: HBASE-9468-trunk-v0.patch
>
>
> 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
