[
https://issues.apache.org/jira/browse/MESOS-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995620#comment-14995620
]
Adam B commented on MESOS-2960:
-------------------------------
commit 1e7be5ca417871828e21c38de07142ee9b2c772e
Author: haosdent huang <haosd...@gmail.com>
Date: Sun Nov 8 00:35:21 2015 -0800
Allow Visibility per port in DiscoveryInfo.
Review: https://reviews.apache.org/r/37022
> 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
> Fix For: 0.26.0
>
>
> 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)
