You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2013/06/10 20:06:32 UTC

[jira] [Resolved] (MESOS-394) Don't do ExecutorLauncher in forked process but exec first instead.

     [ https://issues.apache.org/jira/browse/MESOS-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kone resolved MESOS-394.
------------------------------

       Resolution: Fixed
    Fix Version/s: 0.13.0
         Assignee: Benjamin Hindman
    
> 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
>            Assignee: Benjamin Hindman
>             Fix For: 0.13.0
>
>
> 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