[MESOS-8337] Invalid state transition attempted when agent is lost.

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Component/s: master
• Target Version/s: 1.5.0
• Assignee: James Peach
• Reporter: James Peach
• Created: 15/Dec/17 18:30
• Updated: 12/Jan/18 23:38
• Resolved: 12/Jan/18 23:38

Description

The change in MESOS-7215 can attempt to transition a task from FAILED to LOST when removing a lost agent. This ends up triggering a CHECK that was added in the same patch.

I1214 23:42:16.507931 22396 master.cpp:10155] Removing task mobius-mloop-1512774555_3661616380-xxx with resources disk(allocated: *):200; cpus(allocated: *):0.01; mem(allocated: *):200; ports(allocated: *):[31068-31068, 31069-31069, 31072-31072] of framework afcbfa05-7973-4ad3-8399-4153556a8fa9-3607 on agent daceae53-448b-4349-8503-9dd8132a6828-S4 at slave(1)@17.147.52.220:5 (magent0006.xxx.com)
F1214 23:42:16.507961 22396 master.hpp:2342] Check failed: task->state() == TASK_UNREACHABLE || task->state() == TASK_LOST TASK_FAILED

Issue Links

• relates to: MESOS-7215 Race condition on re-registration of non-partition-aware frameworks