You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Michael K. Edwards (JIRA)" <ji...@apache.org> on 2018/11/21 23:54:00 UTC

[jira] [Commented] (ZOOKEEPER-2440) permanent SESSIONMOVED error after client app reconnects to zookeeper cluster

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16695394#comment-16695394 ] 

Michael K. Edwards commented on ZOOKEEPER-2440:
-----------------------------------------------

Is this patch something that could/should be revived for 3.5.5?

> 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
>            Priority: Major
>             Fix For: 3.6.0, 3.5.5
>
>         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
(v7.6.3#76005)