[
https://issues.apache.org/jira/browse/MESOS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14495123#comment-14495123
]
Benjamin Mahler commented on MESOS-2191:
----------------------------------------
How does that work for custom executors running in the docker containerizer?
Currently schedulers may not necessarily expect data messages to come from
command / docker tasks.
> Add ContainerId to the TaskStatus message
> -----------------------------------------
>
> Key: MESOS-2191
> URL: https://issues.apache.org/jira/browse/MESOS-2191
> Project: Mesos
> Issue Type: Wish
> Components: containerization
> Reporter: Marcel Neuhausler
> Assignee: Alexander Rojas
> Labels: mesosphere
>
> {{TaskStatus}} provides the frameworks with certain information
> ({{executorId}}, {{slaveId}}, etc.) which is useful when collecting
> statistics about cluster performance; however, it is difficult to associate
> tasks to the container it is executed since this information stays always
> within mesos itself. Therefore it would be good to provide the framework
> scheduler with this information, adding a new field in the {{TaskStatus}}
> message.
> See comments for a use case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
