Loading...

XML

Word

Printable

JSON

Details

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.0.4, 4.1.3
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

Description

Since the oplog can never be dropped, there's no need to hold an IX lock on the oplog when writing into it.

Attachments

Issue Links

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

Activity

People

Assignee:: Eric Milkie

Reporter:: Spencer Brody (Inactive)

Participants:: Eric Milkie, Githook User, Michael Cahill, Spencer Brody

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Dates

Created:: Aug 08 2018 07:33:45 PM UTC

Updated:: Oct 29 2023 10:29:08 PM UTC

Resolved:: Aug 24 2018 04:56:16 PM UTC