-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.0.6
-
Component/s: Concurrency, WiredTiger
-
None
-
ALL
-
When many upserts happen at the same time, and the queried document does not exist, there should be only one insert, and the rest of the upserts should result in updates to the inserted document.
In Mongo 3.0 with the WiredTiger engine, more than one document gets inserted in this situation. This does not happen on MMAPv1, or on Mongo 2.6.
- duplicates
-
SERVER-16905 Concurrent upserts to the same non-existing document can result in duplicate key error
- Closed
-
SERVER-14322 Retry on predicate unique index violations of update + upsert -> insert when possible
- Closed
- related to
-
SERVER-16261 Make insert on update (upsert: true) atomic with query + insert
- Closed