-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Concurrency
-
None
-
Storage Execution
-
ALL
some info from SERVER-2184
Fri Dec 3 15:28:33 [initandlisten] shutdown: going to flush oplog...
Fri Dec 3 15:28:33 [initandlisten] shutdown: going to close sockets...
Fri Dec 3 15:28:33 [initandlisten] shutdown: waiting for fs preallocator...
Fri Dec 3 15:28:33 [initandlisten] shutdown: closing all files...
Fri Dec 3 15:28:33 [conn1] end connection 127.0.0.1:58246
Fri Dec 3 15:28:33 [interruptThread] now exiting
Fri Dec 3 15:28:33 dbexit: ; exiting immediately
mongod: /opt/boost/include/boost/thread/pthread/mutex.hpp:50: void boost::mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.
Fri Dec 3 15:28:33 Got signal: 6 (Aborted).
I did an audit for uses of boost mutexes which could potentially trigger the first message reported:
RWLock
- MongoFile / mmmutex
- SpinLock
- NetworkCounter
- ServiceStats ?
- CachedBSONObj ?
- CmdReplSetReconfig
etc.
task / Ret ?
task / Server ?
MVar ?
ClientCursor::ccmutex
Author:
{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}Message: SERVER-2184 clarify usage of mongo mutex
/mongodb/mongo/commit/0b97deb52745f7da9464ddaf11ea2f85f211fa26
- is related to
-
SERVER-2184 Graceful shutdown fails once in a while
- Closed
-
SERVER-695 mutex assertion on shutdown is ugly
- Closed