[SERVER-63308] Accommodate WT-8601 Created: 04/Feb/22 Updated: 29/Oct/23 Resolved: 08/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Task | 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 | ||||||||||||||||
| Sprint: | Execution Team 2022-02-21 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
MDB did rely on using read_timestamp for the oplog, but not in a way where the WT bug could manifest (anything the journal recovers is either rewritten by MDB or no longer a hole where the read_timestamp is meaningful). WT's change for 8601 isn't to fix the bug per-se, but rather to drop timestamp information completely on writes to logged tables. Thus the behavior is consistent and an application can never successfully rely on it existing. This ticket is to transform MDBs usage of read_timestamp on the oplog into the server itself. |
| Comments |
| Comment by Githook User [ 08/Feb/22 ] |
|
Author: {'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}Message: Move read timestamp visibility against the oplog into MongoDB. WiredTiger In MDB, the keys for oplog documents are the object's timestamp. MDB will |