Thanks for the tip. I don't have full access to the machine but at least
something I can ask about.
On 18.05.2018 18:25, Jie Yu wrote:
Hendrik,
It looks to me that Mesos always pass LIBPROCESS_IP to executor if
agent's LIBPROCESS_IP environment variable is set:
https://github.com/apache/mesos/blob/1.4.x/src/slave/slave.cpp#L8106-L8115
Maybe that's the difference between your vanilla Mesos, and DC/OS
Mesos config?
- Jie
On Fri, May 18, 2018 at 2:29 AM, Hendrik Haddorp
<[email protected] <mailto:[email protected]>> wrote:
Hi,
I had been using Mesos 1.4.1 and now tried out a DC/OS setup
(1.9.4) and noticed that the env variable LIBPROCESS_IP was set.
This broke my scheduler (running as a docker container on
Marathon). Things worked fine again once I unset the variable in
my startup script.
I'm now wondering why LIBPROCESS_IP is being set. Is there maybe
some config setting in Mesos that leads to that? MESOS-3553 and
MESOS-3740 are for example about LIBPROCESS_IP being passed on but
as I didn't get it passed in on Mesos 1.4.1 this is odd.
thanks,
Hendrik
