[SERVER-16905] Concurrent upserts to the same non-existing document can result in duplicate key error - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major - P3
Resolution: Duplicate
Affects Version/s: 2.8.0-rc5
Fix Version/s: None
Component/s: Concurrency, Write Ops
Labels:
None
Environment:
2.8.0-rc5, wiredTiger storage engine only

Operating System:
ALL
Steps To Reproduce:

Hide

Run the Java code from this gist: https://gist.github.com/anonymous/5221f3025b549a708299

Expected result:

One thread will "win" and be the one to insert the document. The rest will see the insert and just update the existing document.

Actual result:

Depending on timing, there are 0-4 exceptions thrown indicating a duplicate key error.

Show
Run the Java code from this gist: https://gist.github.com/anonymous/5221f3025b549a708299 Expected result: One thread will "win" and be the one to insert the document. The rest will see the insert and just update the existing document. Actual result: Depending on timing, there are 0-4 exceptions thrown indicating a duplicate key error.

Description

A test program that starts five threads, each repeatedly upserting a document with the same _id to a collection that doesn't initially contain a document with that _id, will encounter duplicate key errors on the first attempt from 0-4 of the five threads, depending on timing.

Attachments

Issue Links

duplicates

SERVER-14322 Retry on predicate unique index violations of update + upsert -> insert when possible

Closed

is duplicated by

SERVER-20380 Upsert is not atomic when inserting

Closed

Activity

People

Assignee:: Unassigned

Reporter:: Jeffrey Yemin

Participants:: Jeffrey Yemin, Scott Hernandez

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Dates

Created:: Jan 16 2015 07:08:54 PM UTC

Updated:: Sep 14 2015 06:14:48 PM UTC

Resolved:: Jan 16 2015 07:19:42 PM UTC