[SERVER-32397] All movement of the oplog read timestamp must notify waiters Created: 19/Dec/17  Updated: 30/Oct/23  Resolved: 20/Dec/17

Status: Closed
Project: Core Server
Component/s: Replication, Storage
Affects Version/s: None
Fix Version/s: 3.6.1, 3.7.1

Type: Bug Priority: Blocker - P1
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: SWNA
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6
Sprint: Repl 2018-01-01
Participants:

 Description   

The main oplog visibility refresh loop separates out setting the oplog read timestamp and notifying waiters. Calls coming in via the external API do not. Advancing the read timestamp in that code path causes the refresh loop to believe the oplog timestamp did not advance and thus not notify any waiters.



 Comments   
Comment by Githook User [ 20/Dec/17 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: SERVER-32397: Notify waiters on any movement of the oplog read timestamp.

(cherry picked from commit 0b7976614d028105a203147fe571b3c264e920b3)
Branch: v3.6
https://github.com/mongodb/mongo/commit/025d4f4fe61efd1fb6f0005be20cb45a004093d1

Comment by Githook User [ 20/Dec/17 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: SERVER-32397: Notify waiters on any movement of the oplog read timestamp.
Branch: master
https://github.com/mongodb/mongo/commit/0b7976614d028105a203147fe571b3c264e920b3

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