[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: |