aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Erb (JIRA)" <>
Subject [jira] [Commented] (AURORA-761) Provide a proxy for generic service discovery
Date Wed, 15 Oct 2014 07:44:34 GMT


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:

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

View raw message