[CURATOR-229] No retry on DNS lookup failure

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.7.0
• Component/s: Framework
• Assignee: Unassigned
• Reporter: Michael Putters
• Created: 02/Jul/15 11:46
• Updated: 17/May/23 10:59
• Resolved: 17/May/23 10:59

Description

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 CuratorFrameworkImpl.java 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.

Issue Links

• duplicates: CURATOR-293 Curator can NOT reconnect after connection lost and session expired when the connection come up while the DNS server is not ready yet.(zookeeper connection string using domain names)