[
https://issues.apache.org/jira/browse/MESOS-6465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15635506#comment-15635506
]
Jie Yu commented on MESOS-6465:
-------------------------------
OK, the plan is to ask default executor to set container_id in container status
and the agent will use that id to get the proper container status for the
nested container.
Given that ContainerStatus is in the task status update, this mapping
information will be available on the master.
> 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: Jie Yu
> 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)
