[SERVER-73633] Refactor the transaction supporting ShardingCatalogManager::commitChunkMigration() Created: 06/Feb/23 Updated: 23/Nov/23 Resolved: 23/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Pol Pinol |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | car-qw, oldshardingemea, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | CAR Team 2023-11-13, CAR Team 2023-11-27 |
| Participants: | |
| Story Points: | 1 |
| Description |
|
The commit of a chunk migration triggers the execution of a transaction with multiple conditional steps, which can summarised as:
Such logic is currently distributed through several future sub-chains, which complicates the understanding of the whole process. The objective of this ticket is to provide a more explicit alternative.
|
| Comments |
| Comment by Githook User [ 22/Nov/23 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: |