[SERVER-79353] (SA) Allow dual `ServerStatusSectionRegistry` based on role Created: 26/Jul/23 Updated: 07/Feb/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | pm-635-milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Service Arch
|
||||||||||||||||||||||||
| Sprint: | Service Arch 2023-08-21, Service Arch 2023-09-04, Service Arch 2023-10-02, Service Arch 2023-10-16, Service Arch 2023-10-30, Service Arch 2023-11-13, Service Arch 2023-11-27, Service Arch 2023-12-11, Service Arch 2023-12-25, Service Arch 2024-01-08, Service Arch 2024-01-22 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
The response provided by the serverStatus command includes a list of "Status" sections, which reflects the state of a group of entities (ServerStatusSection objects) managed by a process-global registry (the ServerStatusSectionRegistry). Such infrastructure needs to be adapted to support a scenario where a mongod process provides role-specific information based on the port serving a serverStatus request. |