Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-8961

Output of tasks gets corrupted if task defines the same environment variables as the executor container

    XMLWordPrintableJSON

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.6.0
    • Fix Version/s: 1.7.0
    • Component/s: containerization
    • Labels:
    • Target Version/s:
    • Sprint:
      Mesosphere Sprint 2018-21
    • Story Points:
      1

      Description

      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:

            if (environment.contains(name) && environment[name] != value) {
              cout << "Overwriting environment variable '" << name << "'" << endl;
            }
      

      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.

        Attachments

          Activity

            People

            • Assignee:
              arojas Alexander Rojas
              Reporter:
              arojas Alexander Rojas
              Shepherd:
              Alex R
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 24h
                24h
                Remaining:
                Remaining Estimate - 24h
                24h
                Logged:
                Time Spent - Not Specified
                Not Specified