[
https://issues.apache.org/jira/browse/MESOS-10194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225465#comment-17225465
]
Jerome Soussens commented on MESOS-10194:
-----------------------------------------
Hi [~asekretenko],
FYI, and just in case it's related to the bug above : we have noticed that,
depending on circumstances, we could send 2 times a final state for a task. For
example, when we kill a task, our custom executor will send 'TASK_KILLED' right
after but at the same time the task could be completed and send a
"TASK_FINISHED" or "TASK_FAILED"... maybe it doesn't help the resource
untracking algorithm ...
> Mesos master failure "Check failed: 'get_(role)' Must be SOME"
> --------------------------------------------------------------
>
> Key: MESOS-10194
> URL: https://issues.apache.org/jira/browse/MESOS-10194
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 1.10.0, 1.11.0
> Reporter: Jerome Soussens
> Assignee: Andrei Sekretenko
> Priority: Critical
> Attachments: log_mesos_crash_role_13102020.txt,
> mesos_scalars_at_slaveId_crash.log
>
>
>
> *Impact* : mesos-master crash with log :
> {code:java}
> hierarchical.cpp:460] Check failed: 'get_(role)' Must be SOME
> {code}
> *Possible scenario :*
> A framework, using a specific role, is stopped. More or less at the same
> time, some remaining task status for this framework comes to the master from
> the executor. But the roles is no more listed.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
