Repository: curator Updated Branches: refs/heads/CURATOR-247 64d966c18 -> 9c7cf5d8b
doc Project: http://git-wip-us.apache.org/repos/asf/curator/repo Commit: http://git-wip-us.apache.org/repos/asf/curator/commit/9c7cf5d8 Tree: http://git-wip-us.apache.org/repos/asf/curator/tree/9c7cf5d8 Diff: http://git-wip-us.apache.org/repos/asf/curator/diff/9c7cf5d8 Branch: refs/heads/CURATOR-247 Commit: 9c7cf5d8ba495bccdea2bcb6b377e95f5f99d521 Parents: 64d966c Author: randgalt <[email protected]> Authored: Sun Aug 23 11:02:19 2015 -0500 Committer: randgalt <[email protected]> Committed: Sun Aug 23 11:02:19 2015 -0500 ---------------------------------------------------------------------- .../apache/curator/framework/CuratorFrameworkFactory.java | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/curator/blob/9c7cf5d8/curator-framework/src/main/java/org/apache/curator/framework/CuratorFrameworkFactory.java ---------------------------------------------------------------------- diff --git a/curator-framework/src/main/java/org/apache/curator/framework/CuratorFrameworkFactory.java b/curator-framework/src/main/java/org/apache/curator/framework/CuratorFrameworkFactory.java index 01a8666..c59d78f 100644 --- a/curator-framework/src/main/java/org/apache/curator/framework/CuratorFrameworkFactory.java +++ b/curator-framework/src/main/java/org/apache/curator/framework/CuratorFrameworkFactory.java @@ -368,11 +368,10 @@ public class CuratorFrameworkFactory * by the CuratorFramework instance. There should be no noticeable differences. * </li> * <li> - * Prior to 3.0.0, an elapsed connection timeout would be presented to the retry policy, possibly - * causing retries. Now, elapsed connection timeouts are only retried if there is an another server - * in the connection string. i.e. a new instance will be retried should the retry policy allow a retry. - * If no other servers remain, a {@link KeeperException.ConnectionLossException} is thrown immediately - * without notifying the retry policy. + * Prior to 3.0.0, each iteration of the retry policy would allow the connection timeout to elapse + * if the connection hadn't yet succeeded. This meant that the true connection timeout was the configured + * value times the maximum retries in the retry policy. This longstanding issue has been address. + * Now, the connection timeout can elapse only once for a single API call. * </li> * <li> * <strong>MOST IMPORTANTLY!</strong> Prior to 3.0.0, {@link ConnectionState#LOST} did not imply
