-
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/global_catalog/ddl/drop_database_coordinator.cpp:323: ATOMICITY 176223 Locking "opCtx->_client".
/src/mongo/db/global_catalog/ddl/drop_database_coordinator.cpp:365: ATOMICITY 176223 Assigning data that might be protected by the lock to "commitTime".
/src/mongo/db/global_catalog/ddl/drop_database_coordinator.cpp:372: ATOMICITY 176223 Unlocking "this->_docMutex". "commitTime" might now be unreliable because other threads can now change the data that it depends on.
/src/mongo/db/global_catalog/ddl/drop_database_coordinator.cpp:372: ATOMICITY 176223 Locking "opCtx->_client" again.
/src/mongo/db/global_catalog/ddl/drop_database_coordinator.cpp:379: ATOMICITY 176223 Using an unreliable value of "commitTime" inside the second locked section. If the data that "commitTime" depends on was changed by another thread, this use might be incorrect.