-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Replication
-
ALL
-
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/repl/primary_only_service.cpp:385: ATOMICITY 175206 Locking "this->_mutex".
/src/mongo/db/repl/primary_only_service.cpp:391: ATOMICITY 175206 Assigning data that might be protected by the lock to "newTerm".
/src/mongo/db/repl/primary_only_service.cpp:408: ATOMICITY 175206 Unlocking "lk". "newTerm" might now be unreliable because other threads can now change the data that it depends on.
/src/mongo/db/repl/primary_only_service.cpp:425: ATOMICITY 175206 Unlocking "this->_mutex". "newTerm" might now be unreliable because other threads can now change the data that it depends on.
/src/mongo/db/repl/primary_only_service.cpp:432: ATOMICITY 175206 Locking "lk" again.
/src/mongo/db/repl/primary_only_service.cpp:438: ATOMICITY 175206 Using an unreliable value of "newTerm" inside the second locked section. If the data that "newTerm" depends on was changed by another thread, this use might be incorrect.