[SERVER-62168] Use --oplogMinRetentionHours in tenant_migration_multi_writes.js to prevent the oplog from being truncated Created: 17/Dec/21  Updated: 29/Oct/23  Resolved: 20/Dec/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.0, 5.2.2

Type: Bug Priority: Major - P3
Reporter: Janna Golden Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.2
Sprint: Server Serverless 2021-12-27
Participants:
Linked BF Score: 49

 Description   

tenant_migration_multi_writes.js is a stress test that runs a ton of writes during tenant migrations, and it's possible for the donor's oplog to get truncated out from under the recipient's oplog fetcher. If this happens, the migration will abort before hitting abortTenantMigrationBeforeLeavingBlockingState and so we'll time out waiting to hit this failpoint. We can use the --oplogMinRetentionHours storage option to prevent the oplog from being truncated.



 Comments   
Comment by Githook User [ 22/Feb/22 ]

Author:

{'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-62168 Use --oplogMinRetentionHours in tenant_migration_multi_writes.js to prevent the oplog from being truncated
Branch: v5.2
https://github.com/mongodb/mongo/commit/99ac18b975425818210e58477202918eb75792c9

Comment by Githook User [ 20/Dec/21 ]

Author:

{'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-62168 Use --oplogMinRetentionHours in tenant_migration_multi_writes.js to prevent the oplog from being truncated
Branch: master
https://github.com/mongodb/mongo/commit/2456a951e6c3abefc68ed4442a088abb4541b66c

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