SERVER-61268 Fixing the release of a recoverable critical section

(cherry picked from commit 071c3d001d4fd11de9d8f644e15ea9bd269ceb35)

1 files changed, 6 insertions, 0 deletions

diff --git a/src/mongo/db/s/shard_server_op_observer.cpp b/src/mongo/db/s/shard_server_op_observer.cpp
index 0998328bc35..6fb7c341cba 100644
--- a/src/mongo/db/s/shard_server_op_observer.cpp
+++ b/src/mongo/db/s/shard_server_op_observer.cpp
@@ -521,6 +521,12 @@ void ShardServerOpObserver::onDelete(OperationContext* opCtx,
 
                     UninterruptibleLockGuard noInterrupt(opCtx->lockState());
                     auto* const csr = CollectionShardingRuntime::get(opCtx, deletedNss);
+
+                    // Secondary nodes must clear the filtering metadata before releasing the
+                    // in-memory critical section
+                    if (!isStandaloneOrPrimary(opCtx))
+                        csr->clearFilteringMetadata(opCtx);
+
                     auto csrLock = CollectionShardingRuntime::CSRLock::lockExclusive(opCtx, csr);
                     csr->exitCriticalSection(csrLock, reason);
                 });