mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-7703) Mesos fails to exec a custom executor when no shell is used
Date Fri, 07 Jul 2017 19:34:00 GMT

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

Jie Yu commented on MESOS-7703:
-------------------------------

commit 6271682e67e0afa4c2d9395f7296e3bebbe909ff
Author: Aaron Wood <aaron.wood@verizon.com>
Date:   Fri Jul 7 11:53:55 2017 -0700

    Searched executables from the current working directory.

    If a framework specifies use of its own executor (in the sandbox) and
    sets shell to false, the executor is never found. This is becase if
    the PATH env variable is set, `execvp` or `execvpe` won't look into
    the current working directory for executables. This patch adds the
    support for searching the current working directory for executables.

    Review: https://reviews.apache.org/r/60280/

> Mesos fails to exec a custom executor when no shell is used
> -----------------------------------------------------------
>
>                 Key: MESOS-7703
>                 URL: https://issues.apache.org/jira/browse/MESOS-7703
>             Project: Mesos
>          Issue Type: Bug
>          Components: agent, executor
>    Affects Versions: 1.2.0, 1.2.1, 1.3.0
>            Reporter: Aaron Wood
>            Assignee: Aaron Wood
>
> If a framework specifies use of its own executor and sets shell to false the executor
is never found.
> {code}
> ...
> I0620 16:27:55.514834 20273 fetcher.cpp:582] Fetched 'http://10.0.2.2:8081/executor'
to '/tmp/slave/slaves/c41232ba-fba1-4d6c-866c-35380d85716f-S0/frameworks/c41232ba-fba1-4d6c-866c-35380d85716f-0000/executors/our_executor/runs/b1d11b00-85bf-428a-a1f0-be8de519294e/executor'
> Failed to execute command: No such file or directory
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message