Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Update custom executor example #27

Open
edi33416 opened this issue Aug 7, 2018 · 3 comments
Open

Update custom executor example #27

edi33416 opened this issue Aug 7, 2018 · 3 comments
Assignees

Comments

@edi33416
Copy link

edi33416 commented Aug 7, 2018

I've been trying to run the mesos-executor as the custom executor, by following the instructions but I wasn't successful.

My custom-executor.json file looks like this

[
    {
        "executor": {
            "name": "theDefaultMesosExecutor",
            "command": {
                "value": "/usr/libexec/mesos/mesos-executor",
                "shell": "true"
            },
            "resources": [
            {
                "name": "cpus",
                "type": "SCALAR",
                "scalar": {
                    "value": 0.1
                }
            },
            {
                "name": "mem",
                "type": "SCALAR",
                "scalar": {
                    "value": 256
                }
            }
            ]
        },
        "task_prefix": "mes-exec-"
    }
]

And I get the following error

I0807 11:22:38.310045 20943 exec.cpp:162] Version: 1.6.0
I0807 11:22:38.317176 20950 exec.cpp:236] Executor registered on agent 7e84b258-a9a7-469d-994b-f5a154b665b5-S1
I0807 11:22:38.319226 20943 executor.cpp:178] Received SUBSCRIBED event
I0807 11:22:38.319492 20943 executor.cpp:182] Subscribed executor on agent-node
I0807 11:22:38.319573 20943 executor.cpp:178] Received LAUNCH event
F0807 11:22:38.325577 20943 executor.cpp:569] Expecting task 'dev-devel-hello_world2-0-fe85afac-67c5-4e07-aac8-2168942a9000' to have a command
*** Check failure stack trace: ***
    @     0x7feb93cb122d  google::LogMessage::Fail()
    @     0x7feb93cb307d  google::LogMessage::SendToLog()
    @     0x7feb93cb0e13  google::LogMessage::Flush()
    @     0x7feb93cb3a79  google::LogMessageFatal::~LogMessageFatal()
    @     0x56158be584f0  mesos::internal::CommandExecutor::launch()
    @     0x56158be5a862  mesos::internal::CommandExecutor::received()
    @     0x56158be5b1bb  _ZNSt17_Function_handlerIFvvEZZNO7process9_DeferredIZN5mesos8internal15CommandExecutor10initializeEvEUlSt5queueINS3_2v18executor5EventESt5dequeIS9_SaIS9_EEEE0_EcvSt8functionIFvT_EEIRKSD_EEvENKUlSM_E_clESM_EUlvE_E9_M_invokeERKSt9_Any_data
    @     0x7feb93bfa9d1  process::ProcessBase::consume()
    @     0x7feb93c1a4fa  process::ProcessManager::resume()
    @     0x7feb93c1aa28  process::ProcessManager::wait()
    @     0x7feb93c1b037  process::wait()
    @     0x56158be1a3b9  main
    @     0x7feb908ff3d5  __libc_start_main
    @     0x56158be1ab05  (unknown)

Thank you!

@ridv ridv self-assigned this Aug 15, 2018
@mauri
Copy link
Contributor

mauri commented Aug 28, 2019

@edi33416 what's the value of the "data" parameter in your ExecutorConfig?

@edi33416
Copy link
Author

edi33416 commented Sep 2, 2019

@mauri I can't remember what the data parameter was. This was related to my internship project which ended last year, and I don't have access to the code anymore.

@edi33416
Copy link
Author

edi33416 commented Sep 2, 2019

I think I tried both leaving the default "" (empty string) value and a simple ls

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants