[
https://issues.apache.org/jira/browse/MESOS-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134476#comment-14134476
]
Connor Doyle commented on MESOS-1795:
-------------------------------------
[~bmahler] I believe so, and those conjectures are outlined in the review.
However if you or others can shed more light on the cause that would be great.
Unfortunately this has been a difficult issue to reproduce.
> Assertion failure in state abstraction crashes JVM
> --------------------------------------------------
>
> Key: MESOS-1795
> URL: https://issues.apache.org/jira/browse/MESOS-1795
> Project: Mesos
> Issue Type: Bug
> Components: java api
> Affects Versions: 0.20.0
> Reporter: Connor Doyle
> Assignee: Connor Doyle
>
> Observed the following log output prior to a crash of the Marathon scheduler:
> Sep 12 23:46:01 highly-available-457-540 marathon[11494]: F0912
> 23:46:01.771927 11532 org_apache_mesos_state_AbstractState.cpp:145]
> CHECK_READY(*future): is PENDING
> Sep 12 23:46:01 highly-available-457-540 marathon[11494]: *** Check failure
> stack trace: ***
> Sep 12 23:46:01 highly-available-457-540 marathon[11494]: @
> 0x7febc2663a2d google::LogMessage::Fail()
> Sep 12 23:46:01 highly-available-457-540 marathon[11494]: @
> 0x7febc26657e3 google::LogMessage::SendToLog()
> Sep 12 23:46:01 highly-available-457-540 marathon[11494]: @
> 0x7febc2663648 google::LogMessage::Flush()
> Sep 12 23:46:01 highly-available-457-540 marathon[11494]: @
> 0x7febc266603e google::LogMessageFatal::~LogMessageFatal()
> Sep 12 23:46:01 highly-available-457-540 marathon[11494]: @
> 0x7febc26588a3 Java_org_apache_mesos_state_AbstractState__1_1fetch_1get
> Sep 12 23:46:01 highly-available-457-540 marathon[11494]: @
> 0x7febcd107d98 (unknown)
> Listing 1: Crash log output.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
