-
Type:
Bug
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
None
-
Storage Execution
-
ALL
-
0
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
One of the automated performance test jobs has seen an EINVAL error return from WT_CURSOR.insert on two occasions. It is possibly triggered by a system availability problem, but there are no obvious system issues logged. We should work to reproduce and understand the issue.
The particular failure is:
file:collection-32-5288585907144325568.wt, WT_CURSOR.insert: encountered an illegal file format or internal value
The stack trace is:
libc.so.6(abort+0x148) [0x7f72d4c008c8] mongod(_ZN5mongo32fassertFailedNoTraceWithLocationEiPKcj+0x0) [0x555ed47afdd5] mongod(+0x12D8016) [0x555ed5245016] mongod(+0x84F645) [0x555ed47bc645] mongod(__wt_err+0x9D) [0x555ed47bc861] mongod(__wt_panic+0x24) [0x555ed47bcab9] mongod(+0x1EECA2A) [0x555ed5e59a2a] mongod(+0x1F0E7A0) [0x555ed5e7b7a0] mongod(+0x1EDCB52) [0x555ed5e49b52] mongod(+0x1F2B914) [0x555ed5e98914] mongod(_ZN5mongo21WiredTigerRecordStore14_insertRecordsEPNS_16OperationContextEPNS_6RecordEm+0x208) [0x555ed522ebd8] mongod(_ZN5mongo21WiredTigerRecordStore13insertRecordsEPNS_16OperationContextEPSt6vectorINS_6RecordESaIS4_EEb+0x31) [0x555ed522ee51] mongod(_ZN5mongo14CollectionImpl16_insertDocumentsEPNS_16OperationContextEN9__gnu_cxx17__normal_iteratorIPKNS_7BSONObjESt6vectorIS5_SaIS5_EEEESB_bPNS_7OpDebugE+0x20E) [0x555ed4988e1e] mongod(_ZN5mongo14CollectionImpl15insertDocumentsEPNS_16OperationContextEN9__gnu_cxx17__normal_iteratorIPKNS_7BSONObjESt6vectorIS5_SaIS5_EEEESB_PNS_7OpDebugEbb+0x176) [0x555ed4989366] mongod(+0xD53D98) [0x555ed4cc0d98] mongod(_ZN5mongo14performInsertsEPNS_16OperationContextERKNS_8InsertOpE+0x826) [0x555ed4cc7026] mongod(_ZN5mongo9CmdInsert7runImplEPNS_16OperationContextERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKNS_7BSONObjERNS_14BSONObjBuilderE+0x4F) [0x555ed4ade33f] mongod(+0xB6CE4B) [0x555ed4ad9e4b]
The test that is failing is insert_ttl.js in a configuration with the oplog enabled (single node replica set). We should attempt to reproduce the failure.