[SERVER-55115] Delete config.collections entry before deleting config.chunks on new DDL paths Created: 10/Mar/21 Updated: 29/Oct/23 Resolved: 10/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1965-Milestone-1, sharding-csrs-stepdown-also | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 126 | ||||||||||||
| Description |
|
Deleting the config.collections entry before the config.chunks entries ensures that a CatalogCache refresh won't see partial chunks. In particular, if we don't do this we may trip this invariant . The CatalogCache refresh could see that the allowMigrations field in config.collections was changed, but the chunk that was bumped along with it may be already deleted by the dropCollection, so the CatalogCache doesn't see a new version. |
| Comments |
| Comment by Githook User [ 10/Mar/21 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |