[SERVER-64248] Don't write resume token noop oplog entry Created: 07/Mar/22  Updated: 29/Oct/23  Resolved: 12/Oct/22

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

Type: Task Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Mathis Bessa
Resolution: Fixed Votes: 0
Labels: shard-merge-milestone-3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-61146 Apply donor oplog entries Closed
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2022-10-17
Participants:

 Description   

TenantMigrationRecipientService::Instance::_enqueueDocuments doesn't need to write a resume token to the oplog if the tenant migration protocol is "shard merge", since Shard Merge isn't resumable.

UPDATE:
Resume token no-op oplog logic isn't added for tenant migration resumability purpose. Resume token no-op oplog entries was added for multi-tenant migration protocol (MTM) to ensure tenant oplog applier reaches clone stop timestamp/block timestamp as MTM fetches only given tenant oplog entries (see SERVER-51246). For shard Merge, we no longer need resume token no-op logic (introduced by SERVER-51246) as shard merge fetches all oplog entries from donor to recipient.

As part of this ticket, shard merge shouldn't request resume token for oplog fetching and shouldn't write the resume token no-op oplog entries.

 



 Comments   
Comment by Githook User [ 12/Oct/22 ]

Author:

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

Message: SERVER-64248 Don't write resume token noop oplog entry
Branch: master
https://github.com/mongodb/mongo/commit/112d7ad9e8eab0c0f8839a98d78b712b2eff9cbd

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