[SERVER-68161] Do not wait for ShardRegistry reload at startup Created: 20/Jul/22 Updated: 29/Oct/23 Resolved: 20/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Tommaso Tocci |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-07-25 |
| Participants: |
| Description |
|
Both for mongos and mongod we wait for ShardRegistry to be populated at startup before considering "sharding" fully initialized. The ShardRegistry is implemented as a ReadThroughCache and will be populated on first access thus there is no need to wait for it to be populated at startup. |
| Comments |
| Comment by Githook User [ 20/Jul/22 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |
| Comment by Githook User [ 20/Jul/22 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |