curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cameron McKenzie (JIRA)" <>
Subject [jira] [Commented] (CURATOR-229) No retry on DNS lookup failure
Date Mon, 10 Apr 2017 23:33:41 GMT


Cameron McKenzie commented on CURATOR-229:

My concern with modifying the start() method functionality is that it breaks the current contract.
The current start() method definition contains no throws clause.

We could possibly introduce a separate start() method that explicitly fails if no connection
to Zookeeper can be established. Would that in conjunction with having control over which
exceptions / errors are retryable solve your respective problems?

> 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
> 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