You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Benjamin Reed (JIRA)" <ji...@apache.org> on 2009/05/29 02:50:45 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 ]
Benjamin Reed updated ZOOKEEPER-22:
-----------------------------------
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.
was:
Moved from SourceForge to Apache.
http://sourceforge.net/tracker/index.php?func=detail&aid=1831412&group_id=209147&atid=1008547
it turns out that all the information to do this is split between server and client. the server pushes all updates through the atomic broadcast, even errors. so if the client resends the pending requests to the server when it reconnects, the server should be able to either replay the responses or execute the request. this would eliminate the annoying-to-deal-with CONNECTIONLOSS error.
> 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
>
> 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.