You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Terra Field (Jira)" <ji...@apache.org> on 2019/10/04 00:22:00 UTC

[jira] [Created] (MESOS-10006) Crash in Sorter: "Check failed: resources.contains(slaveId)"

Terra Field created MESOS-10006:
-----------------------------------

             Summary: Crash in Sorter: "Check failed: resources.contains(slaveId)"
                 Key: MESOS-10006
                 URL: https://issues.apache.org/jira/browse/MESOS-10006
             Project: Mesos
          Issue Type: Bug
          Components: master
    Affects Versions: 1.9.0, 1.4.1, 1.1.0
         Environment: Ubuntu Bionic 18.04, Mesos 1.1.0, 1.4.1, 1.9.0 (logs are from 1.9.0).
            Reporter: Terra Field
         Attachments: mesos-master.log.gz

We've hit a similar exception on 3 different versions of the Mesos master (the line #/file name changes but the Check failed is the same), usually when under very high load:
{noformat}
F1003 22:06:54.463502  8579 sorter.hpp:339] Check failed: resources.contains(slaveId)
{noformat}
This particular occurrence happened after the election of a new master that was then stuck doing framework update broadcasts, as documented in MESOS-10005.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)