mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Rukletsov (JIRA)" <>
Subject [jira] [Commented] (MESOS-8247) Executor registered message is lost
Date Wed, 10 Jan 2018 14:18:00 GMT


Alexander Rukletsov commented on MESOS-8247:
-------------------------------------------- — not a fix, logging improvement.

> Executor registered message is lost
> -----------------------------------
>                 Key: MESOS-8247
>                 URL:
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Andrei Budnik
>            Assignee: Andrei Budnik
> h3. 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.
> h3. Problem description.
> The agent launches built-in docker executor, which is stuck in `STAGING` state.
> stderr logs of the docker executor:
> {code}
> I1114 23:03:17.919090 14322 exec.cpp:162] Version: 1.2.3
> {code}
> 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:
> {code}
> Received killTask for task ...
> {code}
> 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.

This message was sent by Atlassian JIRA

View raw message