Benjamin Mahler created MESOS-366:
-------------------------------------

             Summary: Master check failure during load tests.
                 Key: MESOS-366
                 URL: https://issues.apache.org/jira/browse/MESOS-366
             Project: Mesos
          Issue Type: Bug
            Reporter: Benjamin Mahler
            Assignee: Benjamin Hindman
            Priority: Critical


This was a check failure on the leading master during a load test. The master 
had been leading for ~10 minutes.

F0227 23:45:54.259697  7485 process.cpp:1950] Check failed: outgoing.count(s) > 
0 
*** Check failure stack trace: ***
I0227 23:45:54.260097  7481 hierarchical_allocator_process.hpp:421] Removed 
slave 201302261827-1937777162-5050-50160-6479
    @     0x7f27a21c8e6d  google::LogMessage::Fail()
I0227 23:45:54.262040  7481 hierarchical_allocator_process.hpp:421] Removed 
slave 201302261827-1937777162-5050-50160-5150
    @     0x7f27a21cead7  google::LogMessage::SendToLog()
I0227 23:45:54.263537  7481 hierarchical_allocator_process.hpp:421] Removed 
slave 201302261827-1937777162-5050-50160-9932
    @     0x7f27a21ca71c  google::LogMessage::Flush()
    @     0x7f27a21ca986  google::LogMessageFatal::~LogMessageFatal()
I0227 23:45:54.265025  7481 hierarchical_allocator_process.hpp:421] Removed 
slave 201302261827-1937777162-5050-50160-5207
    @     0x7f27a208541c  process::SocketManager::next()
I0227 23:45:54.266531  7481 hierarchical_allocator_process.hpp:421] Removed 
slave 201302261827-1937777162-5050-50160-9130
    @     0x7f27a2086388  process::send_data()
    @     0x7f27a220ddb3  ev_invoke_pending
I0227 23:45:54.268057  7481 hierarchical_allocator_process.hpp:421] Removed 
slave 201302261827-1937777162-5050-50160-7869
    @     0x7f27a22131e8  ev_loop
    @     0x7f27a2082b70  process::serve()
I0227 23:45:54.269634  7481 hierarchical_allocator_process.hpp:421] Removed 
slave 201302261827-1937777162-5050-50160-10558
    @     0x7f27a17a573d  start_thread
    @     0x7f27a0189f6d  clone

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to