[SERVER-36734] Provide sane TaskExecutor's for administrative tasks Created: 17/Aug/18 Updated: 23/Mar/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Internal Code, Networking |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Backlog - Service Architecture |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | former-quick-wins, re-triaged-ticket | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Sprint: | Service Arch 2018-11-05 | ||||||||
| Participants: | |||||||||
| Description |
|
We have a proliferation of TaskExecutors across Sharding and Replication which are generally used for their background thread (as well as some limited use around specialized hooks). It would dramatically simplify the server if these TaskExecutors all used the same NetworkInterface (and shared the same connection pool) where at all possible. For the thread pool implementation, either a simple unlimited thread pool, or single thread handling callbacks per task executor, would provide much simpler semantics than the current model (re-using the networking thread as the thread pool and requiring a full TaskExecutor + NetworkInterface for each subsystem) |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 02/Nov/21 ] |
|
The Service Arch team is in the process of cleaning up tickets in the backlog. This ticket has not been updated in two years so we are closing it. Please reopen if you think this change is valuable. |