[SERVER-61302] Attempt to unify RecoveryUnit stashing/unstashing logic Created: 05/Nov/21 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
As part of the SBE yielding work, we'll be stashing the RecoveryUnit on ClientCursors for find, aggregate and getMore commands. There is already similar machinery for multi-document transactions, which stores the RecoveryUnit across multiple operations (not just find()/aggregate()/getMore). This is built on the TransactionParticipant and related classes. This task is to investigate and attempt to unify these two functionalities. We may find that the transaction machinery is "too heavyweight" for what we want, or it may end up being a good simplification of the codebase. |