[ZOOKEEPER-22] Automatic request retries on connect failover

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: c client, java client
• Assignee: Mahadev Konar
• Reporter: Patrick D. Hunt
• Created: 10/Jun/08 21:27
• Updated: 25/Sep/23 03:58

Description

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.

Issue Links

• is part of: ZOOKEEPER-835 Refactoring Zookeeper Client Code
• is related to: ZOOKEEPER-1905 ZKClients are hitting KeeperException$ConnectionLossException due to wrong usage pattern
• is related to: ZOOKEEPER-4747 Java api lacks synchronous version of sync() call
• requires: ZOOKEEPER-660 Clean up scripts need to change to clean up transaction logs only for a max timeout period.