You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@aurora.apache.org by "Kevin Sweeney (JIRA)" <ji...@apache.org> on 2015/04/03 21:21:52 UTC

[jira] [Created] (AURORA-1245) Consider not resolving the server hostname at startup

Kevin Sweeney created AURORA-1245:
-------------------------------------

             Summary: Consider not resolving the server hostname at startup
                 Key: AURORA-1245
                 URL: https://issues.apache.org/jira/browse/AURORA-1245
             Project: Aurora
          Issue Type: Story
          Components: Scheduler
            Reporter: Kevin Sweeney
            Priority: Minor


We currently abort startup if we're unable to resolve the scheduler hostname with a reverse DNS lookup. This seems like an unnecessary configuration burden - we could just use the local IP address if the reverse-lookup fails. We also publish this DNS name in ZooKeeper, but we could get away with publishing the the server IP address instead (clients that are finding us via ZooKeeper should be relying on ZooKeeper watch events to learn about changes to the scheduler IP address, not re-resolution of our DNS name every TTL).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)