[
https://issues.apache.org/jira/browse/MESOS-8317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284378#comment-16284378
]
James Peach commented on MESOS-8317:
------------------------------------
/cc [~vinodkone]
> Check failed when newly registered executor has launched tasks.
> ---------------------------------------------------------------
>
> Key: MESOS-8317
> URL: https://issues.apache.org/jira/browse/MESOS-8317
> Project: Mesos
> Issue Type: Bug
> Reporter: James Peach
>
> This check in {{slave/slave.cpp}} can fail:
> {code}
> 4105 if (state != RECOVERING &&
> 4106 executor->queuedTasks.empty() &&
> 4107 executor->queuedTaskGroups.empty()) {
> 4108 CHECK(executor->launchedTasks.empty())
> 4109 << " Newly registered executor '" << executor->id
> 4110 << "' has launched tasks";
> 4111
> 4112 LOG(WARNING) << "Shutting down the executor " << *executor
> 4113 << " because it has no tasks to run";
> 4114
> 4115 _shutdownExecutor(framework, executor);
> 4116
> 4117 return;
> 4118 }
> {code}
> This happens with the following sequence of events:
> 1. HTTP executor subscribes
> 2. Agent sends a LAUNCH message that the executor can't decode
> 3. HTTP executor closes the channel and re-subscribes
> 4. Agent hits the above check because the executor sends and empty task list
> (it never understood the LAUNCH message), but the agent thinks that a task
> should have been launched.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
