[SERVER-71161] Investigate removal of `signalOplogWaiters` in favor of majority committed point notification Created: 08/Nov/22  Updated: 14/Nov/22  Resolved: 14/Nov/22

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

Type: Task Priority: Minor - P4
Reporter: Denis Grebennicov Assignee: Matthew Russotto
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-69959 Introduce majority committed point ad... Closed
Sprint: Repl 2022-11-28
Participants:

 Description   

In SERVER-69959 majority committed point advancement notification mechanism is introduced. Now change streams that are reading through oplog and change collection (in serverless) can benefit from it while waiting for the insertions of the new oplog entries (which are majority committed).

Originally change streams (that are reading the oplog) were relying on the `signalOplogWaiters()`mechanism, which was called once majority committed point advanced. This ticket's purpose is to investigate whether or not this method can be removed as it is no longer needed for the change streams purposes.

Evergreen patch with `signalOplogWaiters()` being removed.



 Comments   
Comment by Matthew Russotto [ 14/Nov/22 ]

The 'signalOplogWaiters()' method is used by replication internally for for the oplog reads done by secondaries (which are done with a local read concern, not majority), so we cannot remove it.

Generated at Thu Feb 08 06:18:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.