[SERVER-65819] Update existing tenant migration retryable writes oplog before startFetchingTimestamp fetcher 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: Mathis Bessa
Resolution: Fixed Votes: 0
Labels: shard-merge-milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

For multi-tenant migration, createRetryableWritesOplogFetchingPipelineForTenantMigrations() fetches only the oplog entries generated by retryable writes with ts < startFetchingTimestamp, specific to a given migrating tenantID. For shard merge protocol, we should fetch oplog entries generated by retryable writes with ts < startFetchingTimestamp for all tenants.



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

Author:

{'name': 'mathisbessamdb', 'email': 'mathis.bessa@mongodb.com', 'username': 'mathisbessamdb'}

Message: SERVER-65819 Update existing tenant migration retryable writes oplog for shard merge
Branch: master
https://github.com/mongodb/mongo/commit/26fd2600a781a7561fc216e38f38932c23bce3f3

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