-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
5
We recently started testing in a SuSe environment with MongoDB, and see errors on shutdown in the form:
2019-05-14T23:07:14.019+0000 E STORAGE [initandlisten] WiredTiger error (16) [1557875234:19015][16136:0x7f9821fd8d40], txn-recover: __wt_cond_destroy, 209: pthread_mutex_destroy: thread group cond: Device or resource busy Raw: [1557875234:19015][16136:0x7f9821fd8d40], txn-recover: __wt_cond_destroy, 209: pthread_mutex_destroy: thread group cond: Device or resource busy 2019-05-14T23:07:14.019+0000 E STORAGE [initandlisten] WiredTiger error (-31804) [1557875234:19053][16136:0x7f9821fd8d40], txn-recover: __wt_panic, 520: the process must exit and restart: WT_PANIC: WiredTiger library panic Raw: [1557875234:19053][16136:0x7f9821fd8d40], txn-recover: __wt_panic, 520: the process must exit and restart: WT_PANIC: WiredTiger library panic 2019-05-14T23:07:14.019+0000 F - [initandlisten] Fatal Assertion 50853 at src/mongo/db/storage/wiredtiger/wiredtiger_util.cpp 410
The relevant call stack is:
mongod(__wt_err_func+0x90) [0x556d588eccbd] mongod(__wt_panic+0x39) [0x556d588ed121] mongod(__wt_thread_group_destroy+0x52) [0x556d58ea4062] mongod(__wt_connection_close+0x17A) [0x556d58e4534a]
There have been bugs in the past in SuSe related to pthread implementations (e.g: https://bugzilla.novell.com/show_bug.cgi?id=865968). We are using a version with fixes for all issues I could find. We should review the eviction thread co-ordination code to make sure it's shutting down threads in a POSIX compliant way.
- is depended on by
-
SERVER-41431 Platform Support: Re-enable SUSE 15 build variants
- Closed
- related to
-
SERVER-41429 Disable SUSE 15 buildvariants
- Closed