[SERVER-16231] Invariant failure when dropping and renaming collections concurrently in WT Created: 19/Nov/14  Updated: 18/Dec/14  Resolved: 16/Dec/14

Status: Closed
Project: Core Server
Component/s: Concurrency, Storage
Affects Version/s: 2.8.0-rc0
Fix Version/s: 2.8.0-rc3

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: 28qa, wiredtiger
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Invariant failure seen == numIndexesTotal(txn) src/mongo/db/catalog/index_catalog.cpp 710
 
thread #12: tid = 0x133385, 0x00007fff93fbc866 libsystem_kernel.dylib`__pthread_kill + 10
  frame #0: 0x00007fff93fbc866 libsystem_kernel.dylib`__pthread_kill + 10
  frame #1: 0x00007fff9383c35c libsystem_pthread.dylib`pthread_kill + 92
  frame #2: 0x00007fff91ba3b1a libsystem_c.dylib`abort + 125
  frame #3: 0x0000000100abe2fc mongod`mongo::invariantFailed(char const*, char const*, unsigned int) + 396
  frame #4: 0x00000001001bf937 mongod`mongo::IndexCatalog::dropAllIndexes(mongo::OperationContext*, bool) + 759
  frame #5: 0x00000001001aea8d mongod`mongo::Database::dropCollection(mongo::OperationContext*, mongo::StringData const&) + 1133
  frame #6: 0x00000001002dab51 mongod`mongo::CmdDrop::run(mongo::OperationContext*, std::string const&, mongo::BSONObj&, int, std::string&, mongo::BSONObjBuilder&, bool) + 1857
  frame #7: 0x00000001002d0315 mongod`mongo::_execCommand(mongo::OperationContext*, mongo::Command*, std::string const&, mongo::BSONObj&, int, std::string&, mongo::BSONObjBuilder&, bool) + 149
  frame #8: 0x00000001002d1a93 mongod`mongo::Command::execCommand(mongo::OperationContext*, mongo::Command*, int, char const*, mongo::BSONObj&, mongo::BSONObjBuilder&, bool) + 4835
  frame #9: 0x00000001002d2816 mongod`mongo::_runCommands(mongo::OperationContext*, char const*, mongo::BSONObj&, mongo::_BufBuilder<mongo::TrivialAllocator>&, mongo::BSONObjBuilder&, bool, int) + 2310
  frame #10: 0x00000001005dee50 mongod`mongo::runCommands(mongo::OperationContext*, char const*, mongo::BSONObj&, mongo::CurOp&, mongo::_BufBuilder<mongo::TrivialAllocator>&, mongo::BSONObjBuilder&, bool, int) + 96
  frame #11: 0x00000001005db6e1 mongod`mongo::newRunQuery(mongo::OperationContext*, mongo::Message&, mongo::QueryMessage&, mongo::CurOp&, mongo::Message&, bool) + 1409
  frame #12: 0x0000000100450af3 mongod`mongo::receivedQuery(mongo::OperationContext*, mongo::Client&, mongo::DbResponse&, mongo::Message&, bool) + 915
  frame #13: 0x000000010044eb28 mongod`mongo::assembleResponse(mongo::OperationContext*, mongo::Message&, mongo::DbResponse&, mongo::HostAndPort const&, bool) + 1160
  frame #14: 0x000000010001183e mongod`mongo::MyMessageHandler::process(mongo::Message&, mongo::AbstractMessagingPort*, mongo::LastError*) + 430
  frame #15: 0x0000000100af3811 mongod`mongo::PortMessageServer::handleIncomingMsg(void*) + 3169
  frame #16: 0x0000000100af4329 mongod`void* boost::_bi::list1<boost::_bi::value<mongo::PortMessageServer::HandleIncomingMsgParam*> >::operator()<void*, void* (*)(void*), boost::_bi::list0>(boost::_bi::type<void*>, void* (*&)(void*), boost::_bi::list0&, long) + 89
  frame #17: 0x0000000100af42c4 mongod`boost::_bi::bind_t<void*, void* (*)(void*), boost::_bi::list1<boost::_bi::value<mongo::PortMessageServer::HandleIncomingMsgParam*> > >::operator()() + 68
  frame #18: 0x0000000100af426c mongod`boost::detail::thread_data<boost::_bi::bind_t<void*, void* (*)(void*), boost::_bi::list1<boost::_bi::value<mongo::PortMessageServer::HandleIncomingMsgParam*> > > >::run() + 28
  frame #19: 0x0000000100b93f64 mongod`boost::(anonymous namespace)::thread_proxy(void*) + 148
  frame #20: 0x00007fff9383b899 libsystem_pthread.dylib`_pthread_body + 138
  frame #21: 0x00007fff9383b72a libsystem_pthread.dylib`_pthread_start + 137
  frame #22: 0x00007fff9383ffc9 libsystem_pthread.dylib`thread_start + 13



 Comments   
Comment by Kamran K. [ 16/Dec/14 ]

This was fixed by the changes from SERVER-16429.

Reproed with 5b44e4b489ef6a8eca4e48d3124665f404cc2c92
No repro with 326d27c5fb249f9d372cb46fd8b97d725b31553a

Generated at Thu Feb 08 03:40:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.