[SERVER-83165] Avoid multiple QuerySettingsManager instances on a multi-role node Created: 13/Nov/23 Updated: 14/Nov/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Romans Kasperovics | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query Execution
|
||||
| Participants: | |||||
| Description |
|
Currently, a QuerySettingsManager is initialized in mongoS and mongoD processes. With PM-635 a single node can be both a router and a shard. In this case a QuerySettingsManager instance (and the corresponding query settings cache) can be shared between router and shard commands, and there is no need for 'ClusterServerParameterRefresher'. |