You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Qian Zhang (JIRA)" <ji...@apache.org> on 2018/01/15 13:50:00 UTC
[jira] [Commented] (MESOS-8446) Agent miss to detach
`virtualLatestPath` for the executor's sandbox during recovery
[ https://issues.apache.org/jira/browse/MESOS-8446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16326250#comment-16326250 ]
Qian Zhang commented on MESOS-8446:
-----------------------------------
RR: https://reviews.apache.org/r/65167/
> Agent miss to detach `virtualLatestPath` for the executor's sandbox during recovery
> -----------------------------------------------------------------------------------
>
> Key: MESOS-8446
> URL: https://issues.apache.org/jira/browse/MESOS-8446
> Project: Mesos
> Issue Type: Bug
> Components: agent
> Reporter: Qian Zhang
> Assignee: Qian Zhang
> Priority: Major
>
> In {{Framework::recoverExecutor()}}, we attach {{executor->directory}} to 3 virtual paths:
> (1) /agent_workdir/frameworks/FID/executors/EID/runs/CID
> (2) /agent_workdir/frameworks/FID/executors/EID/runs/latest
> (3) /frameworks/FID/executors/EID/runs/latest
> But in this method, when we find the executor completes, we only do detach for (1) and (2) but not (3). We should do detach for (3) too as what we do in {{Slave::removeExecutor}}, otherwise, it will be a leak.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)