curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Weston (JIRA)" <>
Subject [jira] [Commented] (CURATOR-229) No retry on DNS lookup failure
Date Thu, 04 Oct 2018 15:29:00 GMT


Sam Weston commented on CURATOR-229:

Has there been any progress on this issue? We are admittedly still running Curator 2.12 and
I've run into this a few times recently due to DNS blips in our Kubernetes cluster. It basically
brings down our entire system until I restart all our services. :(

> No retry on DNS lookup failure
> ------------------------------
>                 Key: CURATOR-229
>                 URL:
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: 2.7.0
>            Reporter: Michael Putters
>            Priority: Major
> Our environment is setup so that host names (rather than IP addresses) are used when
registering services.
> When disconnecting a node from the network, it will attempt to reconnect and - in order
to do this - attempts to resolve a host name, which fails (since we have no network connectivity
and a DNS server is used).
> It appears this type of exception is not retryable, and the node simply gives up and
never reconnects, even when the network connectivity is back.
> Is this the expected behavior? Is there any way to configure Curator so that this type
of exception is retryable? I had a look at {{}} around line 768 but
there doesn't seem to be anything configurable.
> If this is not the expected behavior (or if it is but you don't mind making it configurable),
I should be able to provide a patch via a pull request.

This message was sent by Atlassian JIRA

View raw message