[SERVER-65820] Update existing tenant migration fetch committed transactions entry before startOptime to support shard merge Created: 20/Apr/22  Updated: 29/Oct/23  Resolved: 07/Jul/22

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

Type: Task Priority: Major - P3
Reporter: Suganthi Mani Assignee: Christopher Caplinger
Resolution: Fixed Votes: 0
Labels: milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2022-05-02, Server Serverless 2022-05-16, Server Serverless 2022-05-30, Server Serverless 2022-06-13, Server Serverless 2022-06-27, Server Serverless 2022-07-11
Participants:

 Description   

We need to fetch all committed transaction entries from config.transaction tables, with lastWriteOpTime.ts <= startApplyingDonorTimestamp, before applying donor oplog entries. Currently, we have createCommittedTransactionsPipelineForTenantMigrations() which is used by multi-tenant migration protocol to fetch committed transaction entries only for a given tenant id. We don't need such a complex pipeline for shard merge protocol as we are migrating all tenants from donor. So, simple find command should be suffice for shard merge.



 Comments   
Comment by Githook User [ 07/Jul/22 ]

Author:

{'name': 'Christopher Caplinger', 'email': 'christopher.caplinger@mongodb.com', 'username': 'UnicodeSnowman'}

Message: SERVER-65820: Fetch committed transactions for shard merge
Branch: master
https://github.com/mongodb/mongo/commit/a4cf78269d575d3aa32d92d188857c53b1994d15

Comment by Suganthi Mani [ 20/Apr/22 ]

you can either use this or this as the inspiration for modeling the fetcher for this ticket.

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