[SERVER-63244] Majority reads must round their read timestamp up to the oldest timestamp Created: 03/Feb/22 Updated: 29/Oct/23 Resolved: 11/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Daniel Gomez Ferro |
| 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 | ||||||||||||
| Sprint: | Execution Team 2022-02-21 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 160 | ||||||||||||
| Description |
|
There is a race now where the oldest timestamp can advance past the majority commit point before the read timestamp is set, resulting in a fassert. We should use the "roundup_timestamps=(read=true)" configuration when starting these transactions and then return the actual read timestamp by querying WT. |
| Comments |
| Comment by Githook User [ 11/Feb/22 ] |
|
Author: {'name': 'Daniel Gómez Ferro', 'email': 'daniel.gomezferro@mongodb.com', 'username': 'dgomezferro'}Message: |