Benjamin Hindman created MESOS-394:
--------------------------------------
Summary: Don't do ExecutorLauncher in forked process but exec
first instead.
Key: MESOS-394
URL: https://issues.apache.org/jira/browse/MESOS-394
Project: Mesos
Issue Type: Bug
Reporter: Benjamin Hindman
We've run into numerous issues where we've code executed in forked processes
has deadlocked because resources (i.e., locks) from the parent process were not
cleaned up (i.e., unlocked) in the forked process. Rather than continue this
trend, we should always attempt to minimize the code executed in a forked
process and if we're doing anything fancy do an exec right away. In particular,
we should only be calling async-signal-safe functions in forked code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
