[
https://issues.apache.org/jira/browse/ZOOKEEPER-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated ZOOKEEPER-22:
-----------------------------------
Attachment: zookeeper-22.docx
here is design document for zookeeper-22. I realised that the scope of
zookeeper-22 is much bigger than i had anticipated. This invloves extensive
changes to the leader, connect requests from the client, clean up scripts.
There needs to version checking introduced with this patch so that old clients
work with the new servers and old servers work with the new client, to make it
all backwards compatible.
Given the scope of this jira, i will be creating sub jiras and mark it as part
of this jira since a humongous patch would be hard to get in given that it
would touch all critical parts of zookeeper.
> 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
>
>
> 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.
