qing yan commented on ZOOKEEPER-22:

One suggestion, can we make auto retry an option rather than mandatory?
My concern is what if client wants to abort the operation after receiving 
He needs to either kill the thread or issue an explict undo operation 
afterwards, kind of awkward...

> 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.3.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 is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to