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.
OplogOrder test can read stale all_durable timestamp after rolling back oplog entries
- Votes:
-
0 Vote for this issue
- Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: