[jira] [Commented] (MESOS-2619) Document master-scheduler communication

["Vinod Kone (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596452#comment-14596452 ] 

Vinod Kone commented on MESOS-2619:
-----------------------------------

With HTTP API this would no longer be an issue. It is also explained in the design doc which will be a point of reference.

I'm assuming you wanted this for the existing driver? If yes, then it's definitely worth documenting. Where would you like to see it documented?

Also, this is labelled 'mesosphere'. Is someone going to tackle this soon [~marco-mesos] ?

> 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)