You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Cody Maloney (JIRA)" <ji...@apache.org> on 2015/06/08 22:22:00 UTC
[jira] [Created] (MESOS-2832) Enable configuring Mesos with
environment variables without having them leak to tasks launched
Cody Maloney created MESOS-2832:
-----------------------------------
Summary: Enable configuring Mesos with environment variables without having them leak to tasks launched
Key: MESOS-2832
URL: https://issues.apache.org/jira/browse/MESOS-2832
Project: Mesos
Issue Type: Wish
Reporter: Cody Maloney
Priority: Critical
Currently if mesos is configured with environment variables (MESOS_MODULES), those show up in every task which is launched unless the executor explicitly cleans them up.
If the task being launched happens to be something libprocess / mesos based, this can often prevent the task from starting up (A scheduler has issues loading a module intended for the slave).
There are also cases where it would be nice to be able to change what the PATH is that tasks launch with (the host may have more in the path than tasks are supposed to / allowed to depend upon).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)