[SERVER-73984] setAllowMigrationsAndBumpOneChunk should send the refresh to all shards Created: 14/Feb/23 Updated: 29/Oct/23 Resolved: 01/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v7.0, v6.3
|
||||||||||||||||
| Sprint: | Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 139 | ||||||||||||||||
| Description |
|
If a migration of the last chunk on a shard commits right before we stop migrations in the catalog manager, the refresh will not be sent to that shard (which is a donor of the migration). This means that we do not wait for the critical section on the donor shard, which can cause the ddl which called stopMigrations to continue when it should wait for the migration to complete. Instead of sending the refresh to the shards that own chunks for the migration, we should send it to all shards. |
| Comments |
| Comment by Githook User [ 01/Mar/23 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |