aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-761) Provide a proxy for generic service discovery
Date Tue, 14 Oct 2014 21:04:35 GMT

    [ https://issues.apache.org/jira/browse/AURORA-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171521#comment-14171521
] 

Bill Farner commented on AURORA-761:
------------------------------------

{quote}
getting a randomized SRV record for a healthy backend from consul then connecting to it directly
{quote}

Out of curiosity, what's the plan for dealing with a backend that has moved?  Also, will you
fetch multiple records when the client wants a pool of connections?

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

Mime
View raw message