You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (JIRA)" <ji...@apache.org> on 2009/07/23 23:29:15 UTC
[jira] Updated: (ZOOKEEPER-484) Clients get SESSION MOVED exception
when switching from follower to a leader.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-484:
-----------------------------------
Component/s: server
Fix Version/s: 3.3.0
> Clients get SESSION MOVED exception when switching from follower to a leader.
> -----------------------------------------------------------------------------
>
> Key: ZOOKEEPER-484
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-484
> Project: Zookeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.2.0
> Reporter: Mahadev konar
> Assignee: Mahadev konar
> Priority: Blocker
> Fix For: 3.2.1, 3.3.0
>
>
> When a client is connected to follower and get disconnected and connects to a leader it gets SESSION MOVED excpetion. This is beacuse of a bug in the new feature of ZOOKEEPER-417 that we added in 3.2. All the releases before 3.2 DO NOT have this problem. The fix is to make sure the ownership of a connection gets changed when a session moves from follower to the leader. The workaround to it in 3.2.0 would be to swithc off connection from clients to the leader. take a look at *leaderServers* java property in http://hadoop.apache.org/zookeeper/docs/r3.2.0/zookeeperAdmin.html.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.