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

Posted to issues@mesos.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2019/04/29 09:28:05 UTC

[jira] [Issue Comment Deleted] (MESOS-4816) Expose TaskInfo to Isolators

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

Gavin updated MESOS-4816:
-------------------------
    Comment: was deleted

(was: www.rtat.net)

> Expose TaskInfo to Isolators
> ----------------------------
>
>                 Key: MESOS-4816
>                 URL: https://issues.apache.org/jira/browse/MESOS-4816
>             Project: Mesos
>          Issue Type: Improvement
>          Components: agent, modules
>            Reporter: Connor Doyle
>            Priority: Major
>
> Authors of custom isolator modules frequently require access to the TaskInfo in order to read custom metadata in task labels.
> Currently, it's possible to link containers to tasks within a module by implementing both an isolator and the {{slaveRunTaskLabelDecorator}} hook, and maintaining a shared map of containers to tasks.  This way works, but adds unnecessary complexity.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)