[
https://issues.apache.org/jira/browse/MESOS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174232#comment-15174232
]
Connor Doyle commented on MESOS-4816:
-------------------------------------
Thanks for the update James, my experience with this is also pre-0.28. As I
understand it, {{prepare()}} gets invoked just once per container (for an
executor's first task), so it might not be sufficient given a framework that
launches multiple tasks per executor. However, if {{ContainerConfig}} covers
most uses then maybe this issue can be dropped?
> Expose TaskInfo to Isolators
> ----------------------------
>
> Key: MESOS-4816
> URL: https://issues.apache.org/jira/browse/MESOS-4816
> Project: Mesos
> Issue Type: Improvement
> Components: modules, slave
> Reporter: Connor Doyle
>
> 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
(v6.3.4#6332)
