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-248) Introduce pluggable error handlers
Date Mon, 24 Aug 2015 17:33:45 GMT


ASF GitHub Bot commented on CURATOR-248:

GitHub user Randgalt opened a pull request:

    [CURATOR-248] Introduce pluggable error handlers


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

    $ git pull CURATOR-248

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 #98
commit 45df7ba71f14a5f9751061a7dff956312bfdd421
Author: randgalt <>
Date:   2015-08-24T17:24:06Z

    Initial error policy with two implementations. Also, applied it to LeaderSelector as a

commit 2e1e92e162ef812a9d076695500f0bda8b15b6c5
Author: randgalt <>
Date:   2015-08-24T17:30:33Z


commit 94dff8a5a2ec336a23c05ebe5cdf7e4b117d3925
Author: randgalt <>
Date:   2015-08-24T17:31:52Z

    Added since tags


> Introduce pluggable error handlers
> ----------------------------------
>                 Key: CURATOR-248
>                 URL:
>             Project: Apache Curator
>          Issue Type: Sub-task
>          Components: Framework, Recipes
>            Reporter: Jordan Zimmerman
>             Fix For: 3.0.0
> Currently, Curator recipes handle error conditions by listening for the SUSPENDED connection
state. Some users would like Curator to try to maintain the session if possible. Introduce
a pluggable error handler system. Have an implementation that does the current behavior. Create
another that attempts to wait until session lost.

This message was sent by Atlassian JIRA

View raw message