[SERVER-16510] WiredTiger Crash when inserting documents in a specific order Created: 11/Dec/14  Updated: 11/Dec/14  Resolved: 11/Dec/14

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

Type: Bug Priority: Major - P3
Reporter: Craig Wilson Assignee: Matt Kangas
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-3304 Change comparison order so all Dates ... Closed
Operating System: ALL
Participants:

 Description   

We just started running the .NET driver's test suite against the wired tiger storage engine and ended up crashing the server. I have reproduced the problem in the shell on windows and was told it occurs on OSX as well. The order of the insertions is important. It has to be a Timestamp first followed by a Date on an indexed field. This does not happen on mmapv1 - only wired tiger.

First repro using _id:

db.foo.insert({ _id: new Timestamp() })
db.foo.insert({ _id: new Date() })

Second repro using an index:

db.foo.createIndex({x:1})
db.foo.insert({ x: new Timestamp() })
db.foo.insert({ x: new Date() })



 Comments   
Comment by Eric Milkie [ 11/Dec/14 ]

SERVER-3304 related?

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