[
https://issues.apache.org/jira/browse/MESOS-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14379591#comment-14379591
]
Alexander Rojas commented on MESOS-2191:
----------------------------------------
Hey [~mneuhaus] at this point there's no clear consensus on whether this fix is
needed at all (you can follow the discussion in the patches links). Therefore
we would like to know more about the use case you have. If you can, It would be
really good if you could answer some questions:
# What exactly is your goal, i.e. If you had the mesos Container ID how would
you use it?
# Are you attempting to extract, ultimately the docker container ID? If so, how
would you do it?
# As it is in the code, there's one Container per Executor, so you could
theoretically use the {{ExecutorID}} for the correlation you mention. Why is
that not enough?
# Why is the internal mesos container id sufficient?
I feel you already answer some of the questions already, but I don't think
everybody has understood the purpose of the ticket and why is it sufficient.
> 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)
