[jira] [Commented] (MESOS-6465) Add a task_id -> container_id mapping in state.json

["Adam B (JIRA)" <ji...@apache.org>]

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

Adam B commented on MESOS-6465:
-------------------------------

AFAIK, the master doesn't actually know the containerId of each container since its metadata is recorded before the agent ever knew about the container. We should update TaskStatus.ContainerStatus to include the containerID when the executor/agent reports status back to master, and then the master could display this in /state.

> Add a task_id -> container_id mapping in state.json
> ---------------------------------------------------
>
>                 Key: MESOS-6465
>                 URL: https://issues.apache.org/jira/browse/MESOS-6465
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Kevin Klues
>            Assignee: Kevin Klues
>              Labels: debugging, mesosphere
>
> Currently, there is no way to get the {{container-id}} of a task from hitting the mesos master alone.  You must first hit the master to get the {{task_id -> agent_id}} and {{task_id -> executor_id}} mappings, then hit the corresponding agent with {{agent_id}} to get the {{executor_id -> container_id}} mapping.
> It would simplify things alot if the {{container_id}} information was immediately available in the {{/tasks}} and {{/state}} endpoints of the master itself.



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