Michael Putters created CURATOR-229:
---------------------------------------
Summary: No retry on DNS lookup failure
Key: CURATOR-229
URL: https://issues.apache.org/jira/browse/CURATOR-229
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 no 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
