[jira] [Commented] (MESOS-4816) Expose TaskInfo to Isolators

["Connor Doyle (JIRA)" <ji...@apache.org>]

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

Connor Doyle commented on MESOS-4816:
-------------------------------------

Maybe the {{update}} signature could be expanded like this?

{code:title=include/mesos/slave/isolator.hpp|borderStyle=solid}
  // Update the resources allocated to the container.
  virtual process::Future<Nothing> update(
      const ContainerID& containerId,
      const Resources& resources,
      const Option<TaskInfo>& taskInfo) = 0;
{code}

> 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)