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 2016/12/17 00:14:58 UTC

[jira] [Comment Edited] (MESOS-6807) Design mapping between `TaskInfo` and Job Objects

    [ https://issues.apache.org/jira/browse/MESOS-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15755869#comment-15755869 ] 

Andrew Schwartzmeyer edited comment on MESOS-6807 at 12/17/16 12:14 AM:
------------------------------------------------------------------------

This is the investigation work for the eventual implementation in Mesos-6690.


was (Author: andschwa):
This is the investigation work for the eventual implementation in the linked issue.

> Design mapping between `TaskInfo` and Job Objects
> -------------------------------------------------
>
>                 Key: MESOS-6807
>                 URL: https://issues.apache.org/jira/browse/MESOS-6807
>             Project: Mesos
>          Issue Type: Bug
>          Components: agent
>         Environment: Windows Server 2016
>            Reporter: Andrew Schwartzmeyer
>            Assignee: Andrew Schwartzmeyer
>              Labels: microsoft, windows
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> This issue starts tracking the work of correctly mapping Mesos's `TaskInfo` APIs (as in resource usage limits of particular tasks scheduled on an agent) to [Windows' Job Objects|https://msdn.microsoft.com/en-us/library/windows/desktop/ms684161(v=vs.85).aspx], which are akin to Linux's `cgroup`s.
> Initial time estimate is for the investigation, not implementation.



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