[
https://issues.apache.org/jira/browse/ZOOKEEPER-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422605#comment-15422605
]
Rakesh R commented on ZOOKEEPER-2440:
-------------------------------------
I am moving this out to 3.4.10 for now. Please feel free to discuss the target
version, if needed. Thanks!
> 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.5.3, 3.6.0, 3.4.10
>
> Attachments: ZOOKEEPER-2440.patch
>
>
> 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)
