Will Farrington created AURORA-1192:
---------------------------------------
Summary: Announced aurora leader information does not respect
-hostname flag
Key: AURORA-1192
URL: https://issues.apache.org/jira/browse/AURORA-1192
Project: Aurora
Issue Type: Bug
Components: Scheduler
Affects Versions: 0.7.0
Environment: CentOS 7 x64, AWS
Reporter: Will Farrington
Our aurora-schedulers are configured to use the primary IP address of the host
they run on with the `-hostname` flag.
The announced serverset in zookeeper continues to use the local hostname. Here
is an example of a {{get /aurora/scheduler/member_ID}} from ZK:
{{{"serviceEndpoint":{"host":"ip-172-18-60-156","port":8081},"additionalEndpoints":{"http":{"host":"ip-172-18-60-156","port":8081}},"status":"ALIVE"}}}
In this particular instance, the hostname doesn't resolve, resulting in the
aurora-client being unable to talk to the aurora-scheduler, since the
aurora-client is taking the host key out of the service endpoint.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
