[
https://issues.apache.org/jira/browse/MESOS-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Wood updated MESOS-7703:
------------------------------
Summary: Mesos fails to exec the custom executor when no shell is used
(was: Mesos fails to execvp a custom executor when no shell is used)
> Mesos fails to exec the 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 in
> the ExecutorInfo 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}
> Additionally, the name of the binary is never passed as an argument so
> executors making use of argv[0] will fail. The shell takes care of this for
> you which is why it's not seen when using a shell.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
