[SERVER-32167] do a second majority write on oldPrimary before committed read in read_committed_after_rollback.js Created: 04/Dec/17  Updated: 30/Oct/23  Resolved: 06/Dec/17

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

Type: Bug Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
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
Participants:
Linked BF Score: 0

 Description   

The secondary can lose it's sync source after it replicates the new write, but before it gets the new committed optime here. Doing a second write should ensure that the new committed optime gets propagated.



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

Author:

{'name': 'Judah Schvimer', 'email': 'judah@mongodb.com', 'username': 'judahschvimer'}

Message: SERVER-32167 do a second majority write before committed read in read_committed_after_rollback.js

(cherry picked from commit 0291277c5fb33d5776c2b19dcf42c9bd76bb777f)
Branch: v3.6
https://github.com/mongodb/mongo/commit/14ec4435636aa7ec8bedabed9f8622b1645b3b45

Comment by Githook User [ 06/Dec/17 ]

Author:

{'name': 'Judah Schvimer', 'username': 'judahschvimer', 'email': 'judah@mongodb.com'}

Message: SERVER-32167 do a second majority write before committed read in read_committed_after_rollback.js
Branch: master
https://github.com/mongodb/mongo/commit/0291277c5fb33d5776c2b19dcf42c9bd76bb777f

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