zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2440) permanent SESSIONMOVED error after client app reconnects to zookeeper cluster
Date Tue, 05 Jul 2016 22:51:10 GMT

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

Ryan Zhang commented on ZOOKEEPER-2440:
---------------------------------------

I wonder what's the next step?

> 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)

Mime
View raw message