mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "haosdent (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (MESOS-2960) Configure DiscoveryInfo and Visibility per port
Date Mon, 27 Jul 2015 10:02:04 GMT

     [ https://issues.apache.org/jira/browse/MESOS-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

haosdent reassigned MESOS-2960:
-------------------------------

    Assignee: haosdent

> Configure DiscoveryInfo and Visibility per port
> -----------------------------------------------
>
>                 Key: MESOS-2960
>                 URL: https://issues.apache.org/jira/browse/MESOS-2960
>             Project: Mesos
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: 0.22.1
>            Reporter: Frank Scholten
>            Assignee: haosdent
>              Labels: mesosphere
>
> For Mesos Elasticsearch I like to use DiscoveryInfo to advertise the client port (9200)
with Visibility=EXTERNAL so it can be discovered by load balancers while advertising the transport
port (9300) as Visibility=FRAMEWORK because it is used by nodes to talk too each other and
should not be load balanced.
> However, I can only set one DiscoveryInfo and one visibility, instead of one per port.
I suggest to allow multiple DiscoveryInfo's to be configured with their own visibility.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message