SERVER-43859: Take MODE_IX locks for collection creation.

Two concurrent storage transactions can now create collections with the same
collection name. These transactions will conflict at commit time; the first
committer will win and register their collection into the global catalog. The
losing transactions will bubble a WriteConflictException.

Top-level callers that should fail if the collection already existed must now
check and fail with a NamespaceExists error code. Previously, those callers
could rely on lower level code returning the NamespaceExists error.

Callers that were implicitly creating a collection may retry the operation,
using the now-registered collection.

These transaction-local collections (UncommittedCollections) are returned when
doing any CollectionCatalog::lookup* call.

1 files changed, 1 insertions, 1 deletions

diff --git a/src/mongo/db/ttl.cpp b/src/mongo/db/ttl.cpp
index 0e514afb651..be0ca3fd9c2 100644
--- a/src/mongo/db/ttl.cpp
+++ b/src/mongo/db/ttl.cpp
@@ -144,7 +144,7 @@ private:
             auto uuid = ttlInfo.first;
             auto indexName = ttlInfo.second;
 
-            auto nss = CollectionCatalog::get(opCtxPtr.get()).lookupNSSByUUID(uuid);
+            auto nss = CollectionCatalog::get(opCtxPtr.get()).lookupNSSByUUID(&opCtx, uuid);
             if (!nss) {
                 ttlCollectionCache.deregisterTTLInfo(ttlInfo);
                 continue;