-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Fully Compatible
-
ALL
-
Repl 2026-10-26
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In resume_after_against_oplog.js, there's a race between reading the oplog and reading it again such that an oplog entry written between those 2 reads - even one written by an internal process - changes the resume token. Fix the test to tolerate that possibility.