-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Concurrency, Write Ops
-
None
-
Fully Compatible
-
ALL
-
v4.4, v4.2
-
Execution Team 2020-03-23, Execution Team 2020-04-06
findAndModify takes exclusive database locks for upserts. It should not need to do this as of the finer-grained locks work, nor should it need to take an exclusive collection lock as of SERVER-43859 to create the collection.
Any exclusive db/collection lock acquisitions in findAndModify should be changed to intent exclusive acquisitions.
- is depended on by
-
SERVER-45956 Allow findAndModify with upsert=true inside multi-document transactions
- Closed
- related to
-
SERVER-47665 findAndModify_upsert_no_conflicts.js fails on storage engine without support for document level locking
- Closed
-
SERVER-47123 Remove AutoGetOrCreateDb
- Closed
-
SERVER-46615 Audit and replace all old-style update calls with new update implementation
- Backlog