[SERVER-45109] Modify AsyncDBClient to allow exhaust requests Created: 12/Dec/19 Updated: 29/Oct/23 Resolved: 28/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Janna Golden |
| 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 2019-12-16, Service Arch 2020-01-27, Service Arch 2020-02-10 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Many functions on AsyncDBClient chain via _call(). To allow AsyncDBClient to serve exhaust responses, we need to separate out the "source" part of its pattern as _waitForResponse(). We can then write runExhaustCommand()/runExhaustCommandRequest() commands that call the "source" part as long as OpMsg::kMoreToCome is set. To test this, we'll want a trivial command that we can treat as exhaust with little other logic: sleep. In summary, there are three parts:
|
| Comments |
| Comment by Githook User [ 28/Jan/20 ] |
|
Author: {'email': 'janna.golden@mongodb.com', 'username': 'jannaerin', 'name': 'Janna Golden'}Message: |