[
https://issues.apache.org/jira/browse/AURORA-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172109#comment-14172109
]
Stephan Erb commented on AURORA-761:
------------------------------------
A great advantage of an HAProxy-based approach is that all control resides at
HAProxy/Aurora. However, by using something like the proposed DNS-approach we
push all control to the client. As indicated by Kevin, this is problematic if
the client or any involved DNS server is caching DNS entries too long or even
forever (as done by many JVMs:
http://stackoverflow.com/questions/1256556/any-way-to-make-java-honor-the-dns-caching-timeout-ttl)
Isaac, you mentioned that a call to consul is better than a call to ZK for the
general case of determining a list of healthy backends for an app. Why is that?
> Provide a proxy for generic service discovery
> ---------------------------------------------
>
> Key: AURORA-761
> URL: https://issues.apache.org/jira/browse/AURORA-761
> Project: Aurora
> Issue Type: Story
> Components: Service Discovery, Usability
> Reporter: Bill Farner
> Priority: Minor
>
> While {{Announcer}} provides service registration, we lack a cross-cutting
> answer for service discovery. There are well-known libraries that will do it
> (e.g. finagle), but we need an answer for others. Marathon, for example,
> provides a script called {{haproxy_marathon_bridge}} that reloads
> configuration of HAProxy for this purpose. We could do something similar
> with a mixin {{Process}} that dynamically routes an inbound port to a
> serverset path in ZooKeeper.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
