You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2018/01/03 16:51:00 UTC
[jira] [Updated] (MESOS-8337) Invalid state transition attempted
when agent is lost.
[ https://issues.apache.org/jira/browse/MESOS-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone updated MESOS-8337:
------------------------------
Priority: Blocker (was: Major)
> Invalid state transition attempted when agent is lost.
> ------------------------------------------------------
>
> Key: MESOS-8337
> URL: https://issues.apache.org/jira/browse/MESOS-8337
> Project: Mesos
> Issue Type: Bug
> Components: master
> Reporter: James Peach
> Assignee: James Peach
> Priority: Blocker
>
> 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.
> {noformat}
> 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
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)