[SERVER-51748] TenantMigrationRecipientService::Instance::_shutdownComponents() should not create opCtx if the client already has opCtx. Created: 19/Oct/20  Updated: 29/Oct/23  Resolved: 17/Nov/20

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

Type: Bug Priority: Major - P3
Reporter: Suganthi Mani Assignee: Suganthi Mani
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-52695 Tenant Migration recipient Instance s... Closed
is depended on by SERVER-51734 Enable tenant migration recipient tes... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2020-11-02, Repl 2020-11-16, Repl 2020-11-30
Participants:

 Description   

Here we should create opCtx only if the client doesn't contain an opCtx, Otherwise it leads to invariant failure (Eg. shutdown (signalHandler thread) calls interrupt()).



 Comments   
Comment by Githook User [ 17/Nov/20 ]

Author:

{'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com', 'username': 'smani87'}

Message: SERVER-51748 TenantMigrationRecipientService should not create opCtx if the client already has opCtx while interrupting migration & should join components outside of mutex lock. SERVER-52700 Tenant Migration recipient Instance should return the interrupt status if cloner fails on network error.
Branch: master
https://github.com/mongodb/mongo/commit/0524e1ec03623ad3c9508a79734c725f7b1c29de

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