[SERVER-40973] Incorrect fast count after reconstructing a prepared transaction in initial sync and then aborting it Created: 02/May/19  Updated: 29/Oct/23  Resolved: 30/May/19

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

Type: Bug Priority: Major - P3
Reporter: Samyukta Lanka Assignee: Vesselina Ratcheva (Inactive)
Resolution: Fixed Votes: 0
Labels: prepare_initial_sync
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-40566 Fix fastcount for large transaction f... Closed
is related to SERVER-39762 Fix fastcount after rollback recovery... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2019-06-03
Participants:

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

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-40973 Wait for secondary to replicate abortTransaction entry in initial_sync_test_fixture_test.js
Branch: master
https://github.com/mongodb/mongo/commit/b937ea729a8b2001e2cf8290991977a973896d1c

Comment by Vesselina Ratcheva (Inactive) [ 30/May/19 ]

There is fortunately no actual fastcount bug. Rather, the test needs to ensure that the secondary has replicated the abortTransaction oplog entry before checking the fastcount. Addressed this in the code review.

Comment by Samyukta Lanka [ 14/May/19 ]

This test will be helpful for reproducing the error: https://github.com/mongodb/mongo/blob/6d714be6880ccf630fa97bb07ffa6a111b180e47/jstests/replsets/initial_sync_test_fixture_test.js#L175-L181

This ticket should also address the TODO there.

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