[
https://issues.apache.org/jira/browse/MESOS-7050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852056#comment-15852056
]
Jie Yu commented on MESOS-7050:
-------------------------------
OK, sounds to me that you need to get the output, but you definitely don't need
the `tee` functionality from io switchboard. Can we think about how to get the
output in a way that does not require io switchboard. I think it should be
doable. Just need to make the logger configurable for that container, and
probably introduce an "in-memory" logger.
fork-exec io switchboard for each command health check sounds really
unfortunate and expensive.
> IOSwitchboard FDs leaked when containerizer launch fails -- leads to deadlock
> -----------------------------------------------------------------------------
>
> Key: MESOS-7050
> URL: https://issues.apache.org/jira/browse/MESOS-7050
> Project: Mesos
> Issue Type: Bug
> Reporter: Kevin Klues
> Assignee: Kevin Klues
> Priority: Critical
> Labels: debugging, mesosphere
>
> If the containizer launch path fails before actually
> launching the container, the FDs allocated to the container by the
> IOSwitchboard isolator are leaked. This leads to deadlock in
> the destroy path because the IOSwitchboard does not shutdown until the
> FDs it allocates to the container have been closed. Since the
> switchboard doesn't shutdown, the future returned by its 'cleanup()'
> function is never satisfied.
> We need a general purpose method for closing the IOSwitchboard FDs when
> failing in the launch path.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
