[SERVER-41391] Clear the oplogTruncateAfterPoint timestamp on stepdown Created: 30/May/19  Updated: 29/Oct/23  Resolved: 05/Nov/19

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-41389 Pause the oplog visibility thread in ... Closed
is depended on by SERVER-41392 Modify the _oplogJournalThreadLoop() ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2019-06-17, Execution Team 2019-07-01, Execution Team 2019-07-29, Execution Team 2019-08-12, Execution Team 2019-11-04, Execution Team 2019-11-18
Participants:

 Description   

We will be setting the oplogTruncateAfterPoint continuously in mode PRIMARY so that we can safely replicate before journaling. SERVER-41389 will pause the thread that sets the oplogTruncateAfterPoint in mode SECONDARY, but we are not guaranteed to run batch application, which unsets the oplogTruncateAfterPoint, before potentially stepping up to primary again.

UPDATE: we are pivoting to unsetting the value on stepdown, as opposed to removing the invariant on stepup.



 Comments   
Comment by Githook User [ 05/Nov/19 ]

Author:

{'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@mongodb.com'}

Message: SERVER-41391 clear the oplogTruncateAfterPoint timestamp on stepdown after there are no more active writes
Branch: master
https://github.com/mongodb/mongo/commit/ec44fef95a3e7a6620df1ff67796b9d4566aeecb

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