[SERVER-4496] boost::lock_error on mongod shutdown Created: 15/Dec/11  Updated: 11/Jul/16  Resolved: 16/Apr/12

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 2.1.1

Type: Bug Priority: Major - P3
Reporter: Aaron Staple Assignee: Dwight Merriman
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Saw this after ctrl-c'ing mongod after doing some testing:

Wed Dec 14 18:56:53 dbexit: really exiting now
Logstream::get called in uninitialized state
Wed Dec 14 18:56:53 [journal] exception in dur::groupCommitLL causing immediate shutdown: boost::lock_error
Wed Dec 14 18:56:53 dur4
Wed Dec 14 18:56:53 Got signal: 6 (Abort trap: 6).

Wed Dec 14 18:56:53 Backtrace:
0x104dd1e15 0x10555a78e 0x7fff8b3bccfa 0 0x7fff8b35ba7a 0x1052e8a3e 0x105166c1d 0x10516837a 0x10516557e 0x10556f7d1 0x106f97460 0x7fff8b3688bf 0x7fff8b36bb75
0 mongod 0x0000000104dd1e15 _ZN5mongo15printStackTraceERSo + 37
1 mongod 0x000000010555a78e _ZN5mongo10abruptQuitEi + 446
2 libsystem_c.dylib 0x00007fff8b3bccfa _sigtramp + 26
3 ??? 0x0000000000000000 0x0 + 0
4 libsystem_c.dylib 0x00007fff8b35ba7a abort + 143
5 mongod 0x00000001052e8a3e _ZN5mongo10mongoAbortEPKc + 190
6 mongod 0x0000000105166c1d _ZN5mongo3dur27groupCommitWithLimitedLocksEv + 1421
7 mongod 0x000000010516837a _ZN5mongo3durL2goEv + 154
8 mongod 0x000000010516557e _ZN5mongo3dur9durThreadEv + 718
9 mongod 0x000000010556f7d1 _ZN5boost6detail11thread_dataIPFvvEE3runEv + 25
10 libboost_thread-mt.dylib 0x0000000106f97460 thread_proxy + 160
11 libsystem_c.dylib 0x00007fff8b3688bf _pthread_start + 335
12 libsystem_c.dylib 0x00007fff8b36bb75 thread_start + 13



 Comments   
Comment by auto [ 19/Dec/11 ]

Author:

{u'login': u'dwight', u'name': u'Dwight', u'email': u'dwight@10gen.com'}

Message: SERVER-4496 shutdown sequencing
Branch: master
https://github.com/mongodb/mongo/commit/6ebb6b8e1b7f645f2e91b02387144434542315e4

Comment by Dwight Merriman [ 19/Dec/11 ]

_groupCommitWithLimitedLocks releases its read lock early; that was the thinking with the groupmutex. however, i think you are right about writeexcluder. i'll do that too.

the groupmutex thing is probably not the problem as it is unlikely there is anything to be committed at that point anyway. it may be worth keeping the fix though as it is more correct that would be relying on assumptions.

Comment by Dwight Merriman [ 18/Dec/11 ]

lmk if that helps or if it reads to you that it will fix

Comment by auto [ 18/Dec/11 ]

Author:

{u'login': u'dwight', u'name': u'dwight', u'email': u'dwight@10gen.com'}

Message: SERVER-4496 shutdown stuff
Branch: master
https://github.com/mongodb/mongo/commit/c14b67b558c3c32680b32b801bdc8b2dc5940f03

Comment by Aaron Staple [ 17/Dec/11 ]

Just saw it again.

Comment by Aaron Staple [ 15/Dec/11 ]

Before I saw that I had just run our jstests against the mongod that produced this stack trace.

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