[SERVER-41392] Modify the _oplogJournalThreadLoop() to no longer call waitUntilDurable() and instead update the oplogTruncateAfterPoint Created: 30/May/19  Updated: 18/Nov/19  Resolved: 18/Nov/19

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) 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:
Depends
depends on SERVER-41389 Pause the oplog visibility thread in ... Closed
depends on SERVER-41391 Clear the oplogTruncateAfterPoint tim... Closed
Related
related to SERVER-44703 Complete TODO listed in SERVER-41392 Closed
is related to SERVER-41386 Create a JS test that ensures non-dur... Closed
is related to SERVER-41387 Create a test that ensures the oplogT... Closed
Sprint: Execution Team 2019-11-04, Execution Team 2019-11-18
Participants:

 Description   

WiredTigerOplogManager::_oplogJournalThreadLoop()

  • stop calling waitUntilDurable().
  • call setOplogTruncateAfterPoint to durably update the oplogTruncateAfterPoint to the WT all_committed timestamp.
  • remove the extra logic to wait for ops waiting for durability before proceeding – we will still have the logic to wait for a journal flush call before proceeding with the loop.

Note: this task is expected to improve performance.


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