[SERVER-32725] CSRS nodes should use KeysCollectionClientDirect instead of KeysCollectionClientSharded Created: 16/Jan/18 Updated: 30/Oct/23 Resolved: 01/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| 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: | MaxH, neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2018-02-26, Sharding 2022-12-12 |
| Participants: |
| Description |
|
Currently config server nodes use a KeysCollectionClientSharded to generate and find keys used for signing clusterTime. This class is also used by shards and mongos and involves making network calls to read the keys from the config server. Since each config server replicates the admin.system.keys collection, they can use the KeysCollectionClientDirect (introduced in |
| Comments |
| Comment by Githook User [ 01/Dec/22 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |
| Comment by Githook User [ 01/Dec/22 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |