-
Type:
Bug
-
Resolution: Incomplete
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.4.10
-
Component/s: Index Maintenance, Storage
-
Labels:None
In trying to reconstruct a Head DB, which is essentially a replica, MMS encounter reports an issue building an index. This is happening with 2.4.10.
Looking in the mongod.log, we have this stack trace:
Wed Jun 11 22:15:30.730 [conn1] Assertion failure Lock::isW() src/mongo/db/namespace_details.cpp 133 0xde8c31 0xda9c9d 0xa64119 0xa6a332 0x8dc008 0x8dc902 0x82a565 0x82a827 0x9fc4a5 0xa032f0 0x6eb838 0xdd51fe 0x7fa65c232e9a 0x7fa65b5453fd /opt/mongodb/mms-backup-daemon/mongodb-releases/mongodb-linux-x86_64-2.4.10/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0xde8c31] /opt/mongodb/mms-backup-daemon/mongodb-releases/mongodb-linux-x86_64-2.4.10/bin/mongod(_ZN5mongo12verifyFailedEPKcS1_j+0xfd) [0xda9c9d] /opt/mongodb/mms-backup-daemon/mongodb-releases/mongodb-linux-x86_64-2.4.10/bin/mongod(_ZN5mongo16NamespaceDetails6onLoadERKNS_9NamespaceE+0x139) [0xa64119] /opt/mongodb/mms-backup-daemon/mongodb-releases/mongodb-linux-x86_64-2.4.10/bin/mongod(_ZN5mongo14NamespaceIndex5_initEv+0x192) [0xa6a332] /opt/mongodb/mms-backup-daemon/mongodb-releases/mongodb-linux-x86_64-2.4.10/bin/mongod(_ZN5mongo8DatabaseC1EPKcRbRKSs+0x1d8) [0x8dc008] /opt/mongodb/mms-backup-daemon/mongodb-releases/mongodb-linux-x86_64-2.4.10/bin/mongod(_ZN5mongo14DatabaseHolder11getOrCreateERKSsS2_Rb+0x462) [0x8dc902] /opt/mongodb/mms-backup-daemon/mongodb-releases/mongodb-linux-x86_64-2.4.10/bin/mongod(_ZN5mongo6Client7Context11_finishInitEv+0x65) [0x82a565] /opt/mongodb/mms-backup-daemon/mongodb-releases/mongodb-linux-x86_64-2.4.10/bin/mongod(_ZN5mongo6Client7ContextC1ERKSsS3_b+0x87) [0x82a827] /opt/mongodb/mms-backup-daemon/mongodb-releases/mongodb-linux-x86_64-2.4.10/bin/mongod(_ZN5mongo14receivedInsertERNS_7MessageERNS_5CurOpE+0x415) [0x9fc4a5] /opt/mongodb/mms-backup-daemon/mongodb-releases/mongodb-linux-x86_64-2.4.10/bin/mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0xb10) [0xa032f0] /opt/mongodb/mms-backup-daemon/mongodb-releases/mongodb-linux-x86_64-2.4.10/bin/mongod(_ZN5mongo16MyMessageHandler7processERNS_7MessageEPNS_21AbstractMessagingPortEPNS_9LastErrorE+0x98) [0x6eb838] /opt/mongodb/mms-backup-daemon/mongodb-releases/mongodb-linux-x86_64-2.4.10/bin/mongod(_ZN5mongo17PortMessageServer17handleIncomingMsgEPv+0x42e) [0xdd51fe] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a) [0x7fa65c232e9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7fa65b5453fd] Wed Jun 11 22:15:30.830 [conn1] warning database /data1/HEAD/5392bf27ddc8b03822ac0287/rsGEN1/head/ Retail could not be opened
In which situation do we get this stack trace?