[SERVER-41342] read_committed_stale_history.js must perform continuous writes to ensure majority commit point propagates to secondary Created: 28/May/19  Updated: 29/Oct/23  Resolved: 30/May/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.0.9
Fix Version/s: 3.6.13, 4.0.11

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 0
Labels: None
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 2019-06-03
Participants:
Linked BF Score: 0

 Description   

Due to the revert of SERVER-33248 on 4.0, the majority commit point is not guaranteed to propagate to secondaries without continuous writes in the system. This means that this read can run forever.



 Comments   
Comment by Githook User [ 31/May/19 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-41342 read_committed_stale_history.js must perform continuous writes to ensure majority commit point propagates to secondary

(cherry picked from commit 69fcaf0c9fa15580959dc56b7bb764b5a301685d)
Branch: v3.6
https://github.com/mongodb/mongo/commit/cdc6351dd35447dfb80f96dacfba43705462a062

Comment by Githook User [ 30/May/19 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-41342 read_committed_stale_history.js must perform continuous writes to ensure majority commit point propagates to secondary
Branch: v4.0
https://github.com/mongodb/mongo/commit/69fcaf0c9fa15580959dc56b7bb764b5a301685d

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