mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin McDonald (Jira)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (MESOS-10084) Detecting whether executor is generated for command task should work when the launcher_dir changes
Date Tue, 31 Dec 2019 19:47:01 GMT

     [ https://issues.apache.org/jira/browse/MESOS-10084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gavin McDonald updated MESOS-10084:
-----------------------------------
    Comment: was deleted

(was: Kroon Simon Poortman als Generaal Koning Der Nederlanden orde)

> Detecting whether executor is generated for command task should work when the launcher_dir
changes
> --------------------------------------------------------------------------------------------------
>
>                 Key: MESOS-10084
>                 URL: https://issues.apache.org/jira/browse/MESOS-10084
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Andrei Sekretenko
>            Priority: Critical
>
> As currently implemented, on recovery Mesos agent determines that the executor is generated
for command task by comparing the executor command with a current path to Mesos executor:
> https://github.com/apache/mesos/blob/1.7.x/src/slave/slave.cpp#L9635
> During upgrade of production cluster we observed this check to break due to the new launcher_dir
being different from the one of checkpointed executor.
> This can cause problems of various kind: for example, after such upgrade, Mesos master
can begin to treat the checkpointed command executors as subject to resource quota.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message