You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michi Mutsuzaki (JIRA)" <ji...@apache.org> on 2014/04/23 22:14:16 UTC

[jira] [Updated] (ZOOKEEPER-22) Automatic request retries on connect failover

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michi Mutsuzaki updated ZOOKEEPER-22:
-------------------------------------

    Fix Version/s:     (was: 3.5.0)
                   3.6.0

> Automatic request retries on connect failover
> ---------------------------------------------
>
>                 Key: ZOOKEEPER-22
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-22
>             Project: ZooKeeper
>          Issue Type: New Feature
>          Components: c client, java client
>            Reporter: Patrick Hunt
>            Assignee: Mahadev konar
>             Fix For: 3.6.0
>
>         Attachments: zookeeper-22.docx, zookeeper-22.pdf
>
>
> Moved from SourceForge to Apache.
> http://sourceforge.net/tracker/index.php?func=detail&aid=1831412&group_id=209147&atid=1008547
> When a connection to a ZooKeeper server fails, all of the pending requests
> will return an error. In reality the requests should be resubmitted when
> the client reestablishes a connection to ZooKeeper.
> For read requests, it's no big deal to just reissue the request. For update
> requests, the ZooKeeper must be able to detect if the request has been
> processed and, if so, return the result of the previous execution;
> otherwise, it should process the request.



--
This message was sent by Atlassian JIRA
(v6.2#6252)