[SERVER-45025] Remove WiredTigerOplogManager thread Created: 09/Dec/19  Updated: 08/Apr/20  Resolved: 08/Apr/20

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

Type: Improvement Priority: Major - P3
Reporter: Eric Milkie Assignee: Dianna Hohensee (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-45810 Explore removing the WiredTigerOplogM... Closed
related to SERVER-47258 Refactor the WiredTigerOplogManager Closed
Sprint: Execution Team 2020-04-20
Participants:

 Description   

It has recently become possible to remove the oplog manager thread entirely, and update oplog visibility in the write paths themselves, after every transaction commits. This will simplify the code with no expected reduction in performance.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 08/Apr/20 ]

Closing for the performance reasons described in SERVER-45810, and the performance reasons observed in the CR of SERVER-47258.

Generated at Thu Feb 08 05:07:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.