mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-6465) Add a task_id -> container_id mapping in state.json
Date Mon, 31 Oct 2016 23:29:59 GMT

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

Jie Yu commented on MESOS-6465:
-------------------------------

Relying on TaskStatus.ContainerStatus does not work for nested container because it's always
a 1-1 mapping between task and container.

> 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)

Mime
View raw message