[SERVER-53625] createOplogFetchingPipelineForResharding() should filter out applyOps entries for aborted transactions Created: 06/Jan/21  Updated: 29/Oct/23  Resolved: 19/Jan/21

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

Type: Bug Priority: Major - P3
Reporter: Alexander Taskov (Inactive) Assignee: Max Hirschhorn
Resolution: Fixed Votes: 0
Labels: PM-234-M2, PM-234-T-oplog-fetch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-49892 Continued testing for aggregation pip... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-01-25
Participants:
Story Points: 1

 Description   

The ReshardingAggTest::VerifyPipelineXXXXAbort() tests are currently failing because the applyOps entries are left behind even though there is an abortTransaction entry at then end of the chain. 

There is code in the createOplogFetchingPipelineForResharding() function that appears to filter these entries out but it does not seem to be working according to the tests.



 Comments   
Comment by Githook User [ 19/Jan/21 ]

Author:

{'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}

Message: SERVER-53625 Fix slimOplogForGraphLookup to include if txn was aborted.
Branch: master
https://github.com/mongodb/mongo/commit/9b491c39df4d4523502a4171d9a467ac9557dc35

Generated at Thu Feb 08 05:31:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.