Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.4.0-rc0, 4.7.0
Affects Version/s: None
Component/s: Concurrency, Write Ops
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v4.4, v4.2
Sprint:
Execution Team 2020-03-23, Execution Team 2020-04-06
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Gregory Noma
Reporter:: Maria van Keulen
Participants:: Githook User, Gregory Noma, Maria van Keulen
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Feb 04 2020 07:20:49 PM UTC
Updated:: Oct 29 2023 10:12:34 PM UTC
Resolved:: Apr 01 2020 08:31:41 PM UTC
Confidence Status Last Update:: 19/Mar/20 6:55 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates