[SERVER-52756] Implement a 'disabled' mode for collections Created: 11/Nov/20 Updated: 27/Oct/23 Resolved: 11/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | PM-1965-Milestone-0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Implement a mode, either through going to the Config server, or by putting the DDL participants in a 'disabled' mode so that all CRUD operations for a collection will be rejected, because the collection is undergoing a DDL change. Given the ability to disable migrations through the allowMigrations:false property ( |
| Comments |
| Comment by Kaloian Manassiev [ 11/Feb/21 ] |
|
Done under |