[
https://issues.apache.org/jira/browse/MESOS-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266270#comment-14266270
]
Balaji commented on MESOS-1795:
-------------------------------
Hi
I am able to reproduce consistently the mentioned issue. I run Chronos with 25
jobs that run infinitely on a Single Mesos Server and the Chronos stops after
running for 3 hours throwing the below error
INFO: State T_ct:1419598728000:0:Transformer Node Merger does not exist yet.
Adding to state
F1226 12:58:00.959278 3100 check.hpp:79] Check failed: f.isReady()
*** Check failure stack trace: ***
@ 0x7f0e1165bd3d google::LogMessage::Fail()
@ 0x7f0e1165db7d google::LogMessage::SendToLog()
@ 0x7f0e1165b92c google::LogMessage::Flush()
Dec 26, 2014 12:58:00 PM mesosphere.chaos.http.ChaosRequestLog write
INFO: 124.30.96.196 - audience [26/Dec/2014:12:58:00 +0000] "GET
/scheduler/graph/csv HTTP/1.1" 200 932 "http://XX.XXX.XX.XXX:8081/";
"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/37.0.2062.120 Safari/537.36"
@ 0x7f0e1165e479 google::LogMessageFatal::~LogMessageFatal()
@ 0x7f0e11651f94 _checkReady<>()
@ 0x7f0e1164fe84
Java_org_apache_mesos_state_AbstractState__1_1store_1get
@ 0x7f0e15147148 (unknown)
./bin/start-chronos.bash: line 27: 2766 Aborted (core dumped)
java -Xmx"$heap" -Xms"$heap" -cp "${jar_files[0]}" com.airbnb.scheduler.Main
"${flags[@]}"
> 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)
