[
https://issues.apache.org/jira/browse/HBASE-9468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-9468:
-------------------------
Fix Version/s: 0.96.0
0.98.0
Release Note: Adds option to disable master's attempt at recovering
zookeeper session: i.e. just fail. Set the fail-fast option when you have a
backup master running that you can fail to.
Hadoop Flags: Reviewed
Status: Patch Available (was: Reopened)
patch lgtm. Sending to hadoopqa.
> 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
