[
https://issues.apache.org/jira/browse/MESOS-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985331#comment-14985331
]
Frank Scholten commented on MESOS-2960:
---------------------------------------
Any idea when this gets merged? We really like to use this feature.
> 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
>
> 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)
