[
https://issues.apache.org/jira/browse/MESOS-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596693#comment-14596693
]
Connor Doyle commented on MESOS-2619:
-------------------------------------
[~vinodkone] you're right; this refers to the existing driver, not the HTTP
API. For one, there's no reference to Libprocess on the documentation landing
page (http://mesos.apache.org/documentation/latest/). Adding something there
would be helpful, if only to seed stuck users' search terms. An overview page
could describe the asynchronous-protobuf-over-HTTP design. Perhaps such a page
could also be linked from an FAQ/troubleshooting topic about framework
connection problems. It's great that the HTTP API will simplify some of these
use cases. The existing driver will probably still be around long enough that
it's worth adding docs about it.
[~marco-mesos] correct, I tagged it but am not currently working the issue. We
were using the tag to simply indicate interest back then.
> 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)
