[
https://issues.apache.org/jira/browse/MESOS-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596492#comment-14596492
]
Marco Massenzio commented on MESOS-2619:
----------------------------------------
Not sure why this is under the {{HTTP API}} Epic - the reason it has the
{{mesosphere}} label is (I'm guessing here) because [~cdoyle] reported it. No
one is currently working on this, as far as I know.
> Document master-scheduler communication
> ---------------------------------------
>
> Key: MESOS-2619
> URL: https://issues.apache.org/jira/browse/MESOS-2619
> Project: Mesos
> Issue Type: Bug
> Components: documentation
> Affects Versions: 0.22.0
> Reporter: Connor Doyle
> Labels: mesosphere
>
> New users often stumble on the networking requirements for communication
> between schedulers and the Mesos master.
> It's not explicitly stated anywhere that the master has to talk back to the
> scheduler. Also, some configuration options (like the LIBPROCESS_PORT
> environment variable) are under-documented.
> This problem is exacerbated as many new users start playing with Mesos and
> scheduers in unpredictable networking contexts (NAT, containers with bridged
> networking, etc.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
