Alexander Rojas created MESOS-8961:
--------------------------------------
Summary: Output of tasks gets corrupted if task defines the same
environment variables as the executor container
Key: MESOS-8961
URL: https://issues.apache.org/jira/browse/MESOS-8961
Project: Mesos
Issue Type: Task
Components: containerization
Affects Versions: 1.6.0
Reporter: Alexander Rojas
Assignee: Alexander Rojas
The issue is easily reproducible if one launches a task group and the taks
nested container defines the same set of environment variables as the executor.
In those circumstances, the following [snippet is
activated|https://github.com/apache/mesos/blob/285d82080748cd69044c226950274c7046048c4b/src/slave/containerizer/mesos/launch.cpp#L1057]:
{code}
if (environment.contains(name) && environment[name] != value) {
cout << "Overwriting environment variable '" << name << "'" << endl;
}
{code}
But this is not the only time that this file writes into {{cout}}.
This may be a bad idea because applications which consume the standard output
of a task may end up being corrupted by the container manager output. In these
cases, writing to {{cerr}} should be the right approach.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
