[SERVER-51452] TenantMigrationConflict should store a shared_ptr to the TenantMigrationAccessBlocker Created: 09/Oct/20  Updated: 29/Oct/23  Resolved: 29/Oct/20

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Jason Zhang
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-A
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-10-19, Sharding 2020-11-02
Participants:

 Description   

This ensures that theĀ catch block in the service entry point is able to find out the migration's outcome.

Otherwise, it's unlikely but possible that the migration would have completed and been forgotten by the time the catch block executes.

This ticket should add a test that if the migration is forgotten before the catch block executes, the operation still correctly returns the migration's outcome.



 Comments   
Comment by Githook User [ 28/Oct/20 ]

Author:

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

Message: SERVER-51452 TenantMigrationConflict should store a shared_ptr to the TenantMigrationAccessBlocker
Branch: master
https://github.com/mongodb/mongo/commit/b4cd12f6dddc0d84ca1396176b39260c1777fba8

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