From edb8778350326d2b33f056b1b5f0b25a4b5b444a Mon Sep 17 00:00:00 2001
From: Henrik Edin <henrik.edin@mongodb.com>
Date: Mon, 23 Mar 2020 10:04:42 -0400
Subject: SERVER-47040 LOGV2_FATAL also fasserts

Added LOGV2_FATAL_NOTRACE and LOGV2_CONTINUE to have different behavior.
---
 src/mongo/db/write_concern.cpp | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

(limited to 'src/mongo/db/write_concern.cpp')

diff --git a/src/mongo/db/write_concern.cpp b/src/mongo/db/write_concern.cpp
index 05570734e5e..f7fadb139cc 100644
--- a/src/mongo/db/write_concern.cpp
+++ b/src/mongo/db/write_concern.cpp
@@ -300,9 +300,8 @@ Status waitForWriteConcern(OperationContext* opCtx,
     try {
         switch (writeConcernWithPopulatedSyncMode.syncMode) {
             case WriteConcernOptions::SyncMode::UNSET:
-                LOGV2_FATAL(22550,
+                LOGV2_FATAL(34410,
                             "Attempting to wait on a WriteConcern with an unset sync option");
-                fassertFailed(34410);
             case WriteConcernOptions::SyncMode::NONE:
                 break;
             case WriteConcernOptions::SyncMode::FSYNC: {
-- 
cgit v1.2.1