[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=15635558#comment-15635558
]
Jie Yu commented on MESOS-6465:
---
https://reviews.apache.org/r/53467/
> 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)
[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=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)
[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=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)
[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=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)
[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=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)
