[MESOS-8297] Built-in driver-based executors ignore kill task if the task has not been launched.

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.4.2, 1.5.0
• Component/s: executor
• Labels: mesosphere
• Target Version/s: 1.3.2, 1.4.2, 1.5.0
• Sprint: Mesosphere Sprint 69, Mesosphere Sprint 70, Mesosphere Sprint 71
• Story Points: 5
• Assignee: Alex R
• Reporter: Alex R
• Shepherd: Vinod Kone
• Created: 04/Dec/17 17:59
• Updated: 26/Mar/18 13:27
• Resolved: 22/Dec/17 18:38

Description

If docker executor receives a kill task request and the task has never been launch, the request is ignored. We now know that: the executor has never received the registration confirmation, hence has ignored the launch task request, hence the task has never started. And this is how the executor enters an idle state, waiting for registration and ignoring kill task requests.

Issue Links

• is related to: MESOS-7466 Mesos marathon and docker not synchronized
• relates to: MESOS-8247 Executor registered message is lost