[
https://issues.apache.org/jira/browse/MESOS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15173399#comment-15173399
]
Guangya Liu commented on MESOS-4816:
------------------------------------
[~cdoyle] Can you please show a concrete use case for this? When the isolator
want to access the TaskInfo? Does the isolator want to access all task infos?
The problem with your proposal is that the {{update}} is mainly used to update
executor resources when task/executor is running, and one executor container
will map to multiple tasks but not one task. so the parameter here for
{{TaskInfo}} may need to be a list?
> 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)
