[
https://issues.apache.org/jira/browse/ZOOKEEPER-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828014#action_12828014
]
qing yan commented on ZOOKEEPER-22:
-----------------------------------
CONNECTION LOSS event refers to the situation where connection to ZK cluster(a
quorum of ZK nodes) is lost and application needs to enter the
safe mode, while broken connection to a particular node and failover to another
node can be handled transparently.
> 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.
