[SERVER-71891] Use a local client explicitly in ShardingCatalogManager Created: 06/Dec/22 Updated: 29/Oct/23 Resolved: 15/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.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 | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2022-12-12, Sharding NYC 2022-12-26 |
| Participants: |
| Description |
|
For a config server serving as a shard, getting the config shard Shard type from the ShardRegistry will return a ShardRemote instead of a ShardLocal. ShardingCatalogManager previously only ran on a dedicated config server and was built around using a ShardLocal, so to prevent changing behavior we should make ShardingCatalogManager use a local client explicitly. |
| Comments |
| Comment by Githook User [ 15/Dec/22 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |