[
https://issues.apache.org/jira/browse/ZOOKEEPER-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363435#comment-15363435
]
Michael Han commented on ZOOKEEPER-2440:
----------------------------------------
Hi [~nerdyyatrice] Next step is to get your patch reviewed by at least one
committer and then committed. Committers are busy (they don't work full time on
upstream ZooKeeper) and also we have a pending 3.5.2-alpha release which most
of the committers have been focusing on. So expecting some delay on code
reviews and ping back if you don't hear any feedback for a while.
> 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
>
> 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)
