[SERVER-75274] Make first class sharded indexes support a catalog shard Created: 24/Mar/23 Updated: 29/Oct/23 Resolved: 20/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding NYC 2023-05-01 | ||||
| Participants: | |||||
| Description |
|
PM-2583 added (currently disabled) support for persisted metadata about sharded cluster indexes. In particular, it adds two collections, config.shard.indexes and config.csrs.indexes. Currently, this feature is not compatible with a catalog shard (ie when the config server is serving as a shard) because the methods for creating those collections will only ever make config.csrs.indexes on the config server (and when dropping the collections in setFCV downgrade), so when shard role logic runs on the config server, it will never have the config.shard.indexes collection. |
| Comments |
| Comment by Githook User [ 20/Apr/23 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |