You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Hamza Faran (JIRA)" <ji...@apache.org> on 2015/11/06 02:53:27 UTC

[jira] [Comment Edited] (MESOS-2376) Allow libprocess ip and port to be configured

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

Hamza Faran edited comment on MESOS-2376 at 11/6/15 1:53 AM:
-------------------------------------------------------------

Yes, unless I'm mistaken, it currently seems like the only way to specify on which ports a custom scheduler can bind is to set the LIBPROCESS_\{IP,PORT\} environment variables. We should be able to set this in the constructor of MesosSchedulerDriver as [~mroth] has mentioned above.


was (Author: hfaran):
Yes, unless I'm mistaken, it currently seems like the only way to specify on which ports a custom scheduler can bind is to set the LIBPROCESS_{IP,PORT} environment variables. We should be able to set this in the constructor of MesosSchedulerDriver as [~mroth] has mentioned above.

> Allow libprocess ip and port to be configured
> ---------------------------------------------
>
>                 Key: MESOS-2376
>                 URL: https://issues.apache.org/jira/browse/MESOS-2376
>             Project: Mesos
>          Issue Type: Improvement
>          Components: java api
>            Reporter: Dario Rexin
>            Priority: Minor
>
> Currently if we want to configure the ip libprocess uses for communication, we have to set the env var LIBPROCESS_IP, or LIBPROCESS_PORT for the port. For the Java API this means, that the variable has to be set before the JVM is started, because setting env vars from within JAVA is not possible / non-trivial. Therefore it would be great to be able to pass them in to the constructor.



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