[
https://issues.apache.org/jira/browse/MESOS-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15174848#comment-15174848
]
Guangya Liu commented on MESOS-4816:
------------------------------------
I saw that MESOS-4500 enabled {{Expose ExecutorInfo and TaskInfo for isolators
in prepare()}}, but as [~cdoyle] point out, this is not enough, as {{prepare}}
wil only be invoked just once per container executor, it will not work for some
cases such as Kubernetes and Mesos integration where one executor can manage
many tasks.
Does it make sense to leave this ticket and update the isoloator api of
{{update()}} to pass a list of {{TaskInfo}} to cover more cases?
> 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)
