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

Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2015/12/28 03:40:49 UTC

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

     [ https://issues.apache.org/jira/browse/AURORA-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bill Farner resolved AURORA-1245.
---------------------------------
    Resolution: Won't Fix

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