[SERVER-73992] Use config as config server shard name Created: 14/Feb/23 Updated: 14/Feb/23 Resolved: 14/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Sharding NYC 2023-02-20 |
| Participants: |
| Description |
|
Going forward, the config server will always have a shardIdentity document. Currently it uses the fixed name "catalogShard" to avoid special casing for the existing ShardId::kConfigServerId "config." The special casing was necessary when the config server couldn't handle sharded requests, but now the config server will always have the shard components set up, so the special casing should be unnecessary and we can simplify the system by using "config" as the config server's shardIdentity shard name. |
| Comments |
| Comment by Jack Mulrow [ 14/Feb/23 ] |
|
Same as |