[
https://issues.apache.org/jira/browse/MESOS-8125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346111#comment-16346111
]
Qian Zhang commented on MESOS-8125:
-----------------------------------
commit b6da63ba2a318e911944a3c475ecf472b1ca86e0
Author: Qian Zhang
Date: Sun Jan 28 20:57:23 2018 +0800
Reaped Docker executor only when it can be connected.
Review: https://reviews.apache.org/r/65382
commit 1512d36c55a2a8fd4f85ebb15a1d13c91d0f403b
Author: Qian Zhang
Date: Mon Jan 29 16:20:23 2018 +0800
Fixed a coding error in a log message of Docker containerizer.
Review: https://reviews.apache.org/r/65420
> 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
>
> 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)
