[SERVER-80854] Remove featureFlagUnsplittableCollectionOnNonPrimaryShards after PM-3229 work on the catalog is finished Created: 07/Sep/23 Updated: 03/Nov/23 Resolved: 03/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-3364-Milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | Sharding EMEA 2023-10-30, CAR Team 2023-11-13 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
Currently we have a feature flag that when disabled prevent all the work in PM-3364 to fully take effect, specifically, when disabled, we don't allow unsplittable collections to live in non primary shards. This behavior is transient, while PM-3364 dependent work is completed and queries can use the information of the single chunk on unsplittable collections to route queries. Once we have full compatibility, we can completely remove the feature flag, and leave the desired behavior (allow unsplittable collections to live in non primary shards) to be the default behavior. |
| Comments |
| Comment by Githook User [ 03/Nov/23 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |