-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
ALL
-
CAR Team 2025-09-29
-
1
-
🟥 DDL
-
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/topology/add_shard_coordinator.cpp:238: ATOMICITY 176317 Locking "opCtx->_client".
/src/mongo/db/topology/add_shard_coordinator.cpp:231: ATOMICITY 176317 Assigning data that might be protected by the lock to "database".
/src/mongo/db/topology/add_shard_coordinator.cpp:238: ATOMICITY 176317 Unlocking "this->this->_docMutex". "database" might now be unreliable because other threads can now change the data that it depends on.
/src/mongo/db/topology/add_shard_coordinator.cpp:238: ATOMICITY 176317 Locking "opCtx->_client" again.
/src/mongo/db/topology/add_shard_coordinator.cpp:243: ATOMICITY 176317 Using an unreliable value of "database" inside the second locked section. If the data that "database" depends on was changed by another thread, this use might be incorrect.
- is related to
-
SERVER-110604 Coverity analysis defect 176048: Value not atomically updated
-
- Closed
-