mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-2190) Use TaskInfo.task_id as ContainerId of a Docker container
Date Fri, 12 Dec 2014 05:03:13 GMT

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

Timothy Chen commented on MESOS-2190:
-------------------------------------

Can you create a JIRA about adding ContainerId into StatusMessage? It will be relevant to
all Mesos developers.

> Use TaskInfo.task_id as ContainerId of a Docker container 
> ----------------------------------------------------------
>
>                 Key: MESOS-2190
>                 URL: https://issues.apache.org/jira/browse/MESOS-2190
>             Project: Mesos
>          Issue Type: Wish
>          Components: containerization
>            Reporter: Marcel Neuhausler
>
> The containerId of a Docker container gets generated by the mesos-slave: "mesos-"+random
UUID. That makes it pretty hard to correlate a Mesos task as shown in Mesos with a container
in for example cAdvisor.
> A quick hack that could make that correlation easier: Use the TaskInfo.TaskID instead
of the randomly generated UUID. In slave.cpp replace:
> containerId.set_value(UUID::random().toString());
> with:
> containerId.set_value(taskInfo.task_id().value());
> Or at least make the Task_Id part of the Container_Id.
> mesos-TaskId-UUID
> Any thoughts?
> --Marcel



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message