You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Neil Conway (JIRA)" <ji...@apache.org> on 2017/06/24 21:48:00 UTC

[jira] [Created] (MESOS-7719) CHECK failure in mesos-execute with old master

Neil Conway created MESOS-7719:
----------------------------------

             Summary: CHECK failure in mesos-execute with old master
                 Key: MESOS-7719
                 URL: https://issues.apache.org/jira/browse/MESOS-7719
             Project: Mesos
          Issue Type: Bug
            Reporter: Neil Conway
            Assignee: Neil Conway


If the master does not support reservation refinement, {{mesos-execute}} might hit a {{CHECK}} failure:

{noformat}
*** Check failure stack trace: ***
    @        0x113042b9a  google::LogMessage::Fail()
    @        0x1130408b5  google::LogMessage::SendToLog()
    @        0x113041609  google::LogMessage::Flush()
    @        0x11304a268  google::LogMessageFatal::~LogMessageFatal()
    @        0x113043085  google::LogMessageFatal::~LogMessageFatal()
    @        0x111c3b70d  mesos::v1::Resources::isEmpty()
    @        0x111c3db03  mesos::v1::Resources::Resource_::isEmpty()
    @        0x111c363f1  mesos::v1::Resources::add()
    @        0x111c4db2a  mesos::v1::Resources::operator+=()
    @        0x111c3e63b  mesos::v1::Resources::operator+=()
    @        0x111c3eb6d  mesos::v1::Resources::Resources()
    @        0x111c3ec0d  mesos::v1::Resources::Resources()
    @        0x10f39374d  CommandScheduler::offers()
    @        0x10f3823d3  CommandScheduler::received()
    @        0x10f38cd2c  _ZZN7process8dispatchI16CommandSchedulerNSt3__15queueIN5mesos2v19scheduler5EventENS2_5dequeIS7_NS2_9allocatorIS7_EEEEEESC_EEvRKNS_3PIDIT_EEMSE_FvT0_ET1_ENKUlPNS_11ProcessBaseEE_clESN_
    @        0x10f38cb40  _ZNSt3__128__invoke_void_return_wrapperIvE6__callIJRZN7process8dispatchI16CommandSchedulerNS_5queueIN5mesos2v19scheduler5EventENS_5dequeISA_NS_9allocatorISA_EEEEEESF_EEvRKNS3_3PIDIT_EEMSH_FvT0_ET1_EUlPNS3_11ProcessBaseEE_SQ_EEEvDpOT_
    @        0x10f38c869  _ZNSt3__110__function6__funcIZN7process8dispatchI16CommandSchedulerNS_5queueIN5mesos2v19scheduler5EventENS_5dequeIS9_NS_9allocatorIS9_EEEEEESE_EEvRKNS2_3PIDIT_EEMSG_FvT0_ET1_EUlPNS2_11ProcessBaseEE_NSB_ISQ_EEFvSP_EEclEOSP_
    @        0x112e8d5ba  std::__1::function<>::operator()()
    @        0x112e8d4fc  process::ProcessBase::visit()
    @        0x112efa73e  process::DispatchEvent::visit()
    @        0x10f381001  process::ProcessBase::serve()
    @        0x112e880d6  process::ProcessManager::resume()
    @        0x112f68cb0  process::ProcessManager::init_threads()::$_1::operator()()
    @        0x112f688d2  _ZNSt3__114__thread_proxyINS_5tupleIJZN7process14ProcessManager12init_threadsEvE3$_1EEEEEPvS6_
    @     0x7fffde14693b  _pthread_body
    @     0x7fffde146887  _pthread_start
    @     0x7fffde14608d  thread_start
{noformat}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)