[SERVER-29882] Automated testing encountered EINVAL return for WT_CURSOR.insert Created: 28/Jun/17  Updated: 27/Oct/23  Resolved: 24/Jun/19

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

Type: Bug Priority: Major - P3
Reporter: Alexander Gorrod Assignee: Backlog - Storage Execution Team
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Storage Execution
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

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.



 Comments   
Comment by Sara Williamson [ 24/Jun/19 ]

This hasn't come up again, so closing as gone away.

Comment by Sulabh Mahajan [ 04/Jul/17 ]

I have the insert_ttl.js test running in a loop on the machine that I setup, and haven't seen this issue in the last 150 runs.
The test successfully completes without hitting any bug in all those runs.
I am going to put this ticket on backlog, while I work with the perf team to reproduce this issue.

Comment by Sulabh Mahajan [ 30/Jun/17 ]

I have setup a machine running insert_ttl.js in a loop, waiting for this bug to be reproduced.

Generated at Thu Feb 08 04:22:04 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.