[SERVER-71655] relax multi-timestamp constraint for muti-doc transactions outside logOplogEntries Created: 28/Nov/22 Updated: 29/Oct/23 Resolved: 09/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| 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: | Execution Team 2022-12-12 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The logOplogEntries() function (within the OpObserverImpl implementation) formats applyOps oplog entries for multi-doc transactions and batched writes. In order to write out a chain of applyOps oplog entries and to write to the images collection while creating the oplog entries, it has to relax the multi-timestamp constraint on the RecoveryUnit. It would be beneficial in terms of separating the applyOps formatting logic from storage engine related settings to be able to update the RecoveryUnit prior to calling logOplogEntries(). This supports the work in |
| Comments |
| Comment by Githook User [ 08/Dec/22 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: The information for relaxing the multi-timestamp constraint is available before calling |
| Comment by Githook User [ 08/Dec/22 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: This allows logOplogEntries() to focus on the formatting logic. Checking |
| Comment by Githook User [ 08/Dec/22 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |