[SERVER-65971] Avoid/Suppress mixed_mode write on config.transactions Created: 26/Apr/22 Updated: 29/Oct/23 Resolved: 26/Jul/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Daniel Gottlieb (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Linked BF Score: | 6 | ||||||||||||||||||||||||||||||||
| Description |
|
When writing to config.transaction documents, we make an optimization to only write the latest value. This can happen for vectored inserts on a primary or after an batch of oplog application. However, after rolling back, we're expected to have the appropriate version of config.transactions documents as of the stable timestamp. Because the storage engine may never have been told about the document, we fix this by synthesizing the right version and persisting it without a timestamp. That update violates the ordered constraint. |
| Comments |
| Comment by Githook User [ 26/Jul/22 ] |
|
Author: {'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}Message: |
| Comment by Githook User [ 26/Jul/22 ] |
|
Author: {'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}Message: |