[MESOS-1795] Assertion failure in state abstraction crashes JVM

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.20.0
• Fix Version/s: 0.22.1, 0.23.0
• Component/s: java api
• Target Version/s: 0.22.1
• Assignee: Joris Van Remoortere
• Reporter: Connor Doyle
• Shepherd: Niklas Quarfot Nielsen
• Created: 15/Sep/14 20:11
• Updated: 02/Jul/15 04:20
• Resolved: 29/Mar/15 20:07

Description

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.

Issue Links

• blocks: MESOS-2579 0.22.1 release
• is duplicated by: MESOS-1804 the "store" component cause on-top framework (chronos) crash
• relates to: MESOS-2161 AbstractState JNI check fails for Marathon framework