diff options
| author | seanzimm <sean.zimmerman@mongodb.com> | 2022-08-05 14:20:44 +0000 |
|---|---|---|
| committer | Evergreen Agent <no-reply@evergreen.mongodb.com> | 2022-08-05 15:05:57 +0000 |
| commit | b994453a33ba0ddf0ea53d3a83c386ded4db9fbc (patch) | |
| tree | f447210e95ce6e354480abfb6454280e30991905 /src/mongo/db/ops | |
| parent | f03bf14cb7ce043bacfdbaeabcd80eb6b416dae6 (diff) | |
| download | mongo-b994453a33ba0ddf0ea53d3a83c386ded4db9fbc.tar.gz | |
SERVER-67617 Stop using ErrorCategory::Interruption in Replication
Diffstat (limited to 'src/mongo/db/ops')
| -rw-r--r-- | src/mongo/db/ops/write_ops_exec.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mongo/db/ops/write_ops_exec.cpp b/src/mongo/db/ops/write_ops_exec.cpp index 9bbd2871678..2cac79f8cbe 100644 --- a/src/mongo/db/ops/write_ops_exec.cpp +++ b/src/mongo/db/ops/write_ops_exec.cpp @@ -193,7 +193,7 @@ public: // here. No-op updates will not generate a new lastOp, so we still need the // guard to fire in that case. Operations on the local DB aren't replicated, so they // don't need to bump the lastOp. - replClientInfo().setLastOpToSystemLastOpTimeIgnoringInterrupt(_opCtx); + replClientInfo().setLastOpToSystemLastOpTimeIgnoringCtxCancelled(_opCtx); LOGV2_DEBUG(20888, 5, "Set last op to system time: {timestamp}", |