-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Storage Execution
-
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/index_builds/multi_index_block.cpp:1229: ATOMICITY 177278 Locking "opCtx->_client".
/src/mongo/db/index_builds/multi_index_block.cpp:1197: ATOMICITY 177278 Assigning data that might be protected by the lock to "indexCatalogEntry".
/src/mongo/db/index_builds/multi_index_block.cpp:1199: ATOMICITY 177278 Unlocking "interceptor->_multikeyPathMutex". "indexCatalogEntry" might now be unreliable because other threads can now change the data that it depends on.
/src/mongo/db/index_builds/multi_index_block.cpp:1229: ATOMICITY 177278 Locking "opCtx->_client" again.
/src/mongo/db/index_builds/multi_index_block.cpp:1235: ATOMICITY 177278 Using an unreliable value of "indexCatalogEntry" inside the second locked section. If the data that "indexCatalogEntry" depends on was changed by another thread, this use might be incorrect.