[SERVER-82033] Adapt existing FTDC controller to shard and router services Created: 10/Oct/23 Updated: 02/Nov/23 Resolved: 20/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pol Pinol | Assignee: | Pol Pinol |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 35 | ||||||||||||||||
| Description |
|
The goal of this ticket is to add FTDCController as a decoration on the new Service object, not ServiceContext. With that, we will ensure that we will have an instance of the FTDCController for each Service, i.e., to a ClusterRole (Shard or Router). Supporting two instances of the FTDCController for a single process (e.g. embedded router) is not a goal of this ticket. |
| Comments |
| Comment by Githook User [ 19/Oct/23 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: |