James DeFelice created MESOS-7839: ------------------------------------- Summary: io switchboard: clarify expected behavior when using TTYInfo with the default executor of a TaskGroup Key: MESOS-7839 URL: https://issues.apache.org/jira/browse/MESOS-7839 Project: Mesos Issue Type: Bug Affects Versions: 1.2.1 Reporter: James DeFelice
I executed a LaunchGroup operation with an Executor of a DEFAULT type and with TTYInfo set to a non-empty protobuf. The tasks of the group did not specify a ContainerInfo. Mesos "successfully" launched the task group and in the executor sandbox stderr reported {code} The io switchboard server failed: Failed redirecting stdout: Input/output error {code} ... which seems relatively uninformative. Mesos also returned TASK_RUNNING followed by TASK_FINISHED for the tasks in the launched group. This wasn't what I expected: my goal was to launch a pod and have a TTY attached to the first task in the group. After discussing with [~klueska] the solution to my problem was to specify TTYInfo for the container of the task within the group, not on the group's executor. But we agreed that Mesos could probably exhibit better behavior in the initial scenario that I tested. Some (mutually exclusive) possibilities for alternate Mesos behavior: (a) fail-fast: using the Default Executor with a task group doesn't support TTYInfo so Mesos should just refuse to launch the task group (and return an appropriate error code and message w/ a reasonable explanation). (b) support TTYInfo when using the Default Executor with a task group. The use case for this is unclear. (c) when using TTYInfo with the DefaultExecutor and task group, attach the TTY to the first task in the group. -- This message was sent by Atlassian JIRA (v6.4.14#64029)