Details
-
Bug
-
Status: Accepted
-
Major
-
Resolution: Unresolved
-
1.3.2, 1.4.1, 1.5.0
-
None
-
None
-
None
Description
Brief description of successful agent-executor communication.
Executor sends `RegisterExecutorMessage` message to Agent during initialization step. Agent sends a `ExecutorRegisteredMessage` message as a response to the Executor in `registerExecutor()` method. Whenever executor receives `ExecutorRegisteredMessage`, it prints a `Executor registered on agent...` to stderr logs.
Problem description.
The agent launches built-in docker executor, which is stuck in `STAGING` state.
stderr logs of the docker executor:
I1114 23:03:17.919090 14322 exec.cpp:162] Version: 1.2.3
It doesn't contain a message like `Executor registered on agent...`. At the same time agent received `RegisterExecutorMessage` and sent `runTask` message to the executor.
stdout logs consists of the same repeating message:
Received killTask for task ...
Also, the docker executor process doesn't contain child processes.
Currently, executor doesn't attempt to launch a task if it is not registered at the agent, while task killing doesn't have such a check.
It looks like `ExecutorRegisteredMessage` has been lost.
Attachments
Issue Links
- is related to
-
MESOS-8297 Built-in driver-based executors ignore kill task if the task has not been launched.
- Resolved