[
https://issues.apache.org/jira/browse/ZOOKEEPER-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357591#comment-15357591
]
Hadoop QA commented on ZOOKEEPER-2440:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12815510/ZOOKEEPER-2440.patch
against trunk revision 1750739.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 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 (version 2.0.3)
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:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3258//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3258//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3258//console
This message is automatically generated.
> permanent SESSIONMOVED error after client app reconnects to zookeeper cluster
> -----------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2440
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2440
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum
> Affects Versions: 3.5.0
> Reporter: Ryan Zhang
> Assignee: Ryan Zhang
> Fix For: 3.4.9, 3.5.3, 3.6.0
>
>
> ZOOKEEPER-710 fixed the issue when the request is not a multi request.
> However, the multi request is handled a little bit differently as the code
> didn't throw the SESSIONMOVED exception. In addition, the exception is set in
> the request by the leader so it will be lost in the commit process and by the
> time the final processor sees it, it will be gone.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
