[SERVER-41389] Pause the oplog visibility thread in mode SECONDARY 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-41391 Clear the oplogTruncateAfterPoint tim... Closed
depends on SERVER-44180 replicationBatchIsComplete() should p... Closed
is depended on by SERVER-41392 Modify the _oplogJournalThreadLoop() ... Closed
Sprint: Execution Team 2019-06-17, Execution Team 2019-11-04, Execution Team 2019-11-18
Participants:

 Description   

In secondary mode, secondary batch application logic already handles visibility and holes in the oplog. Both the in-memory oplogReadTimestamp and the persisted oplogTruncateAfterPoint are updated. There's no need for the oplog visibility thread to run and use resources doing unnecessary work. (plus it would get confusing with batch application unsetting the oplogTruncateAfterPoint while the oplog visibility thread keeps setting it)


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