You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Kapil Arya (JIRA)" <ji...@apache.org> on 2015/07/14 03:27:05 UTC

[jira] [Created] (MESOS-3039) Allow executors binding IP to be different than Slave binding IP

Kapil Arya created MESOS-3039:
---------------------------------

             Summary: Allow executors binding IP to be different than Slave binding IP
                 Key: MESOS-3039
                 URL: https://issues.apache.org/jira/browse/MESOS-3039
             Project: Mesos
          Issue Type: Bug
            Reporter: Kapil Arya
            Assignee: Kapil Arya
            Priority: Critical


Currently, the Slave will bind either to the loopback IP (127.0.0.1) or to the IP passed via the `--ip` flag. When it launches a containerized executor (e.g, via Mesos Containerizer), the executor inherits the binding IP of the Slave. This is due to the fact that the `--ip` flags sets the environment variable `LIBPROCESS_IP` to the passed IP. The executor then inherits this environment variable and is forced to bind to the Slave IP.

If an executor is running in its own containerized environment, with a separate IP than that of the Slave, currently there is no way of forcing it to bind to its own IP. A potential solution is to use the executor environment decorator hooks to update LIBPROCESS_IP environment variable for the executor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)