[
https://issues.apache.org/jira/browse/AURORA-1212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371446#comment-14371446
]
Brian Brazil commented on AURORA-1212:
--------------------------------------
> How do you deal with port conflicts?
We have manual port assignment, backed by a wiki page. The static ports are
disjoint from the range aurora/mesos assign from.
> If these types of tasks are not dedicated, how do the clients discover the
> host(s) they are on?
The same as dedicated hosts, you use all mesos hosts. We may do something a bit
smarter in future, but that requires writing a central coordinator to ensure we
don't restart too many haproxies at once.
For internal traffic we'll be using ribbon and serversets.
> Have you considered alternative approaches like those mentioned in
> AURORA-761, or mesos-dns?
Unfortunately none of those approaches work with ELB->HAProxy in a sane way
that doesn't lose queries.
http://www.boxever.com/gracefully-shutting-down-haproxy-with-elb explains we
currently do to avoid losing queries.
> Allow non-dedicated jobs to have static ports
> ---------------------------------------------
>
> Key: AURORA-1212
> URL: https://issues.apache.org/jira/browse/AURORA-1212
> Project: Aurora
> Issue Type: Story
> Reporter: Brian Brazil
>
> In my environment I'd like to have static ports for some jobs to integrate
> with some services that don't do service discovery, but I don't want to have
> to partition my users up onto dedicated machines just for this.
> Currently the aurora client rejects such a configuration, it should be
> allowed.
> https://github.com/apache/incubator-aurora/commit/bcabfce60d568d5d98c72109ee4493bce773a426
> was where this restriction was added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
