[
https://issues.apache.org/jira/browse/MESOS-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Hindman resolved MESOS-2832.
-------------------------------------
Resolution: Fixed
Fix Version/s: 0.23.0
commit 46dc9979e9cc38d36dc7300db13af39bdfbfd52e
Author: Benjamin Hindman <benjamin.hind...@gmail.com>
Date: Mon Jun 15 00:29:20 2015 -0700
Added 'executor_environment_variables' flag to slave.
This new flag, 'executor_environment_variables', let's an operator
specify the environment variables that should be passed to an
executor, and thus, any of it's tasks. By default, an executor will
inherit the environment variables of the slave.
Review: https://reviews.apache.org/r/35567
> 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
> Assignee: Benjamin Hindman
> Priority: Critical
> Labels: mesosphere
> Fix For: 0.23.0
>
>
> 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)
