[SERVER-54539] Make command execution mindful of the threading model Created: 12/Feb/21 Updated: 29/Oct/23 Resolved: 26/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Amirsaman Memaripour | Assignee: | Amirsaman Memaripour |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Service Arch 2021-03-08 | ||||
| Participants: | |||||
| Description |
|
The asynchronous implementations for the buildInfo command are designed to work with the fixed-thread pool for client connections. However, they are currently in the default execution path and unaware of the threading model (defined here). We should have the execution to fallback to the synchronous implementation for dedicated threading models. This ticket should change the invocations of CommandHelpers::runCommandInvocationAsync in strategy.cpp and service_entry_point_common.cpp to fallback to CommandHelpers::runCommandInvocation for dedicated threading models. |
| Comments |
| Comment by Githook User [ 26/Feb/21 ] |
|
Author: {'name': 'Amirsaman Memaripour', 'email': 'amirsaman.memaripour@mongodb.com', 'username': 'samanca'}Message: |