[SERVER-36883] support non-doc-locking storage engines in SERVER-36534 Created: 27/Aug/18  Updated: 29/Oct/23  Resolved: 27/Aug/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.0.4, 4.1.3

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Eric Milkie
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-50018 lock order is reversed when updating ... Closed
is related to SERVER-36534 Don't acquire locks on oplog when wri... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Storage NYC 2018-09-10
Participants:
Case:
Linked BF Score: 0

 Comments   
Comment by Githook User [ 30/Oct/18 ]

Author:

{'name': 'Eric Milkie', 'email': 'milkie@10gen.com', 'username': 'milkie'}

Message: SERVER-36883 lock oplog for non-doc-locking storage engines

(cherry picked from commit 820fca1bc1c3698c3b4577f4644bf8dbadf91fc0)
Branch: v4.0
https://github.com/mongodb/mongo/commit/34f10cf10cfc5294f1e24367bfea6d0592da0759

Comment by Githook User [ 27/Aug/18 ]

Author:

{'name': 'Eric Milkie', 'email': 'milkie@10gen.com', 'username': 'milkie'}

Message: SERVER-36883 lock oplog for non-doc-locking storage engines
Branch: master
https://github.com/mongodb/mongo/commit/820fca1bc1c3698c3b4577f4644bf8dbadf91fc0

Generated at Thu Feb 08 04:44:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.