[SERVER-54039] Tenant migration timeout cancellation token is not used properly Created: 25/Jan/21  Updated: 29/Oct/23  Resolved: 08/Feb/21

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

Type: Bug Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: Jason Zhang
Resolution: Fixed Votes: 0
Labels: pm-1791_other_required
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-51081 Add a way to "try abort" a tenant mig... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-02-22
Participants:

 Description   

There was a large refactoring that removed theĀ `recipientSyncDataCommandCancelSource` token from the argument list of the `_sendRecipientSyncDataCommand` around line 637.

Please see the current code where token becomes unused:
https://github.com/mongodb/mongo/blob/ca9f854ac4b7f9197a0574f72e450a8317696286/src/mongo/db/repl/tenant_migration_donor_service.cpp#L629



 Comments   
Comment by Githook User [ 08/Feb/21 ]

Author:

{'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}

Message: SERVER-54114 SERVER-54039 Pass cancelation token throughout TenantMigrationDonorService
Branch: master
https://github.com/mongodb/mongo/commit/3120087175678ec7a61a6d12cd9326ba8cfa2d45

Comment by Andrew Shuvalov (Inactive) [ 25/Jan/21 ]

The test to use is jstests/replsets/tenant_migration_blocking_state_timeout.js

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