Hadoop QA commented on ZOOKEEPER-484:

+1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 800990.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 6 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
Findbugs warnings: 
Console output: 

This message is automatically generated.

> 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
>         Attachments: sessionTest.patch, ZOOKEEPER-484.patch
> 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.

Reply via email to