You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Andrew Schwartzmeyer (JIRA)" <ji...@apache.org> on 2017/01/26 00:01:26 UTC

[jira] [Assigned] (MESOS-6892) Reconsider process creation primitives on Windows

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

Andrew Schwartzmeyer reassigned MESOS-6892:
-------------------------------------------

    Assignee: Andrew Schwartzmeyer  (was: Alex Clemmer)

> Reconsider process creation primitives on Windows
> -------------------------------------------------
>
>                 Key: MESOS-6892
>                 URL: https://issues.apache.org/jira/browse/MESOS-6892
>             Project: Mesos
>          Issue Type: Bug
>          Components: stout
>            Reporter: Alex Clemmer
>            Assignee: Andrew Schwartzmeyer
>              Labels: microsoft
>
> Windows does not have the same notions of process hierarchies as Unix, and so killing groups of processes requires us to make sure all processes are contained in a job object, which acts something like a cgroup. This is particularly important when we decide to kill a task, as there is no way to reliably do this unless all the processes you'd like to kill are in the job object.
> This causes us a number of issues; it is a big reason we needed to fork the command executor, and it is the reason tasks are currently unkillable in the default executor.
> As we clean this issue up, we need to think carefully about the process governance semantics of Mesos, and how we can map them to a reliable, simple Windows implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)