Uploaded image for project: 'Apache Curator'
  1. Apache Curator
  2. CURATOR-229

No retry on DNS lookup failure

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.7.0
    • Fix Version/s: None
    • Component/s: Framework
    • Labels:
      None

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mput Michael Putters
            • Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated: