-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Engines, Storage Engines - Server Integration
-
ALL
-
Sleepysaurus - 2025-10-14
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Value not atomically updated
The result of the update will be determined by the interleaving of thread execution. Non-atomic update of a concurrently shared value
/src/mongo/db/storage/wiredtiger/wiredtiger_oplog_manager.cpp:213: ATOMICITY 176625 Locking "lk".
/src/mongo/db/storage/wiredtiger/wiredtiger_oplog_manager.cpp:219: ATOMICITY 176625 Assigning data that might be protected by the lock to "deadline".
/src/mongo/db/storage/wiredtiger/wiredtiger_oplog_manager.cpp:228: ATOMICITY 176625 Unlocking "lk". "deadline" might now be unreliable because other threads can now change the data that it depends on.
/src/mongo/db/storage/wiredtiger/wiredtiger_oplog_manager.cpp:228: ATOMICITY 176625 Locking "lk" again.
/src/mongo/db/storage/wiredtiger/wiredtiger_oplog_manager.cpp:228: ATOMICITY 176625 Using an unreliable value of "deadline" inside the second locked section. If the data that "deadline" depends on was changed by another thread, this use might be incorrect.