[SERVER-71055] OplogOrder test can read stale all_durable timestamp after rolling back oplog entries Created: 03/Nov/22 Updated: 29/Oct/23 Resolved: 08/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.1, 5.0.15, 6.0.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | Gregory Noma |
| 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 | ||||||||
| Backport Requested: |
v6.1, v6.0, v5.0, v4.4, v4.2
|
||||||||
| Sprint: | Execution Team 2022-11-14 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 5 | ||||||||
| Description |
|
The OplogOrder unit test rolls back two oplog entries and then checks that oplog visibility ruled are still honored. However, because the all_durable timestamp is not being updated to reflect this, the WiredTigerOplogManager can run and incorrectly move the oplog visibility timestamp forward again to its old value. |
| Comments |
| Comment by Githook User [ 16/Nov/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: (cherry picked from commit 9eb32dfc24d692013c38e69d9cce0f9c8655c40c) |
| Comment by Githook User [ 16/Nov/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: (cherry picked from commit 9eb32dfc24d692013c38e69d9cce0f9c8655c40c) |
| Comment by Githook User [ 08/Nov/22 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |