[SERVER-53107] Tenant Migration related jstests should call donorForgetMigration when migration is completed(aborted/committed). Created: 30/Nov/20  Updated: 29/Oct/23  Resolved: 04/Jan/21

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

Type: Task Priority: Major - P3
Reporter: Suganthi Mani Assignee: Pavithra Vetriselvan
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-B
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-48814 Handle cleanup in MigrationServiceIns... Closed
Related
is related to SERVER-53109 Fix tenant_migration_conflicting_dono... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-12-14, Repl 2020-12-28, Repl 2021-01-11
Participants:

 Description   

Tenant Migration related jstests should call donorForgetMigration when migration is completed(aborted/committed). Failure to do so will make the recipient to exhaust the TenantMigrationRecipientService thread pool (default is 8, see SERVER-50669). Currently, there are components on the recipient side, like oplog fetcher and cloner, which runs a synchronous task on the TenantMigrationRecipientService thread pool without yielding the thread. Those components will be stopped only if the migration on recipient side fails due to an error or receives RecipientForgetMigration cmd.



 Comments   
Comment by Ian Whalen (Inactive) [ 04/Jan/21 ]

Author:

{'username': u'evrg-bot-webhook', 'name': u'Pavi Vetriselvan', 'email': u'pavithra.vetriselvan@mongodb.com'}

Message:SERVER-53107 Tenant migration tests should use donorForgetMigration when the migration commits/aborts
Branch:master
https://github.com/mongodb/mongo/commit/e3699082acb1a3e41e2b781c6beb039e7b90a030

Comment by Suganthi Mani [ 30/Nov/20 ]

CC lingzhi.deng

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