curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CURATOR-239) RetryPolicy that retries forever
Date Thu, 23 Jul 2015 23:09:04 GMT


ASF GitHub Bot commented on CURATOR-239:

GitHub user leandronunes85 opened a pull request:

    CURATOR-239 - RetryPolicy that retries forever


You can merge this pull request into a Git repository by running:

    $ git pull CURATOR-239

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #94
commit 6e8c10847d4b453a1a1aeafcb6c58f51889f2d1f
Author: Leandro Nunes <>
Date:   2015-07-23T23:06:26Z

    CURATOR-239 - Adding RetryForever retry policy


> RetryPolicy that retries forever
> --------------------------------
>                 Key: CURATOR-239
>                 URL:
>             Project: Apache Curator
>          Issue Type: Wish
>          Components: Client
>            Reporter: Leandro Nunes
>            Assignee: Jordan Zimmerman
>            Priority: Trivial
> I'd like to have a RetryPolicy that never ceases to retry. I find having to come up with
number for maxRetries a pain. I mean, I guess it makes sense to have my clients repeatedly
trying to connect to zookeeper on most cases. I can be missing something though (this seems
so obvious to me that I most definitely am).

This message was sent by Atlassian JIRA

View raw message