mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qian Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-8125) Agent should properly handle recovering an executor when its pid is reused
Date Wed, 31 Jan 2018 02:42:00 GMT

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

Qian Zhang commented on MESOS-8125:
-----------------------------------

For the issue that Docker containerizer does not recover the executor pid, I created a separate
ticket for it: https://issues.apache.org/jira/browse/MESOS-8515.

> Agent should properly handle recovering an executor when its pid is reused
> --------------------------------------------------------------------------
>
>                 Key: MESOS-8125
>                 URL: https://issues.apache.org/jira/browse/MESOS-8125
>             Project: Mesos
>          Issue Type: Bug
>          Components: docker
>            Reporter: Gastón Kleiman
>            Assignee: Qian Zhang
>            Priority: Critical
>             Fix For: 1.6.0
>
>
> Here's how to reproduce this issue:
> # Start a task using the Docker containerizer (the same will probably happen with the
command executor).
> # Stop the corresponding Mesos agent while the task is running.
> # Change the executor's checkpointed forked pid, which is located in the meta directory,
e.g., {{/var/lib/mesos/slave/meta/slaves/latest/frameworks/19faf6e0-3917-48ab-8b8e-97ec4f9ed41e-0001/executors/foo.13faee90-b5f0-11e7-8032-e607d2b4348c/runs/latest/pids/forked.pid}}.
I used pid 2, which is normally used by {{kthreadd}}.
> # Reboot the host



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message