-
Type:
Task
-
Status: Closed
-
Priority:
Major - P3
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Replication, Storage
-
Labels:None
-
Backwards Compatibility:Fully Compatible
-
Backport Requested:v4.0, v3.6
-
Sprint:Storage NYC 2018-08-27
-
Case:
-
Linked BF Score:36
Since the oplog can never be dropped, there's no need to hold an IX lock on the oplog when writing into it.
- related to
-
SERVER-35367 Hold locks in fewer callers of waitForAllEarlierOplogWritesToBeVisible()
-
- Closed
-
-
SERVER-36883 support non-doc-locking storage engines in SERVER-36534
-
- Closed
-
-
SERVER-40498 Writing transaction oplog entries must not take locks while holding an oplog slot
-
- Closed
-
-
SERVER-36514 Hold lock on oplog as soon as optime is reserved
-
- Closed
-