You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Kevin Klues (JIRA)" <ji...@apache.org> on 2016/11/03 19:20:58 UTC

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

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

Kevin Klues commented on MESOS-6465:
------------------------------------

Jie can you comment on how you plan to do this now?

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