[SERVER-72088] Make catalog shard use ShardRemote for config server in ShardRegistry Created: 13/Dec/22 Updated: 29/Oct/23 Resolved: 03/Jan/23 |
|
| 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 | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
All sharding components expect getting the config shard from the ShardRegistry returns a ShardRemote (e.g. expects to be able to target secondaries, not just the local node), but the config server currently always returns a ShardLocal as the config shard. To allow a config server to serve a shard role, we should have it return a ShardRemote instead. |
| Comments |
| Comment by Githook User [ 21/Dec/22 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |
| Comment by Githook User [ 20/Dec/22 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: Revert " This reverts commit 07118e1f61dddb68170b7aa095166028b284d687. |
| Comment by Githook User [ 20/Dec/22 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |