[
https://issues.apache.org/jira/browse/HBASE-9468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13765037#comment-13765037
]
Hudson commented on HBASE-9468:
-------------------------------
SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #723 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/723/])
HBASE-9468 Previous active master can still serves RPC request when it is
trying recovering expired zk session (stack: rev 1521959)
* /hbase/trunk/src/main/docbkx/configuration.xml
HBASE-9468 Previous active master can still serves RPC request when it is
trying recovering expired zk session (stack: rev 1521949)
* /hbase/trunk/hbase-common/src/main/resources/hbase-default.xml
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java
> 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, 0.94.13
>
> Attachments: 9468-0.94.txt, 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
