[SERVER-55895] Unfreeze migrations in rename coordinator Created: 08/Apr/21 Updated: 27/Oct/23 Resolved: 09/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | PM-1965-Milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Sprint: | Sharding EMEA 2021-05-03 |
| Participants: |
| Description |
|
The rename coordinator is currently freezing migrations on source and destination collections, but not unblocking them upon finishing. Migrations should be reactivated as last step of the coordinator. |
| Comments |
| Comment by Pierlauro Sciarelli [ 09/Apr/21 ] |
|
Closing because the current protocol is correct: the source CollectionType is saved by the coordinator before stopping migrations, hence migrations are allowed right after the metadata rename. Move chunks will serialize on the critical section within each node, waiting for the local rename to finish. |