11601 — Interrupted

queryconcurrency

The operation was interrupted by a killOp or similar mechanism

What is happening?

Interrupted is returned when a running operation is killed before it completes. This can happen through db.killOp(), maxTimeMS expiry on the server side, cursor.close(), or internal server processes interrupting operations during shutdown preparation or state transitions. Unlike InterruptedAtShutdown (11600) or InterruptedDueToReplStateChange (11602), this code is a general interruption without a specific cause category.

Common causes

  1. An administrator ran db.killOp() on the operation
  2. The operation exceeded an internal time limit
  3. A cursor was closed or abandoned while the server was processing getMore
  4. maxTimeMS was set and the server-side limit was reached
  5. The operation was interrupted during server preparation for shutdown

Diagnostic Steps

Related Issues

SERVER-113458Closed
CheckMetadataConsistency should report if FCV upgrade have left legacy timeseries collections
During upgrade to FCV 9.0 timeseries collections will be converted automatically to viewless timeseries . The conversion will start after the cluster (including the config server) have already transitioned to FCV 9.0 and before the setFeatureComatibilityVersion command returns the response to the user. This means that if the conversion is interrupted by an error (e.g. network error, primary stepdown etc..) it will be the responsibility of the user or automation agent to keep retrying the setFeat
SERVER-135359Backlog
Fix the recovery duration metrics reporting after node restarts in Authoritative Shards Dashboard Recovery
After investigating several spikes of recovery times from the dashboard as part of [HELP-100264|https://jira.mongodb.org/browse/HELP-100264], it was concluded that all of the spikes that exceed 1sec follow the same pattern. There was a recovery initiated, but it was interrupted by the user/automation in Atlas, which was observed through the following log in the mongod: For the next 15 seconds, the cluster wasn't accepting any requests and doing any work, reporting that it entered the quies
SERVER-121413Closed
Track the number of times the KEK has been used to encrypt DEKs
From a security perspective, we need to guarantee that a KEK has not been used 2^32-1 times to perform encryption. This follows a security guideline outlined by section 8.3 of [NIST GCM recommendations|section 8.3 of https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38d.pdf]. This will likely have to be persisted in the keystore itself.
SERVER-137945Backlog
Store MCV and NDV in persistent stats
SERVER-90264Closed
Remove slow step from compile
SERVER-130498Closed
Strictly validate the names of the FLE2 ESC and ECOC state collections
h1. Security Context See SECBUG-1031 for problem description, security impact, preconditions, reproduction steps, and severity rationale. h1. Root Cause Authorization is checked only on the user-facing EDC namespace; the internal state collection names supplied by the client in encryptionInformation are never validated against the EDC collection or authorized separately. +*Gap 1 — isFLE2StateCollection validates format only, not derivation*+ src/mongo/crypto/encryption_fields_valida
SERVER-125892Blocked
Add HostUnreachable to retryable errors in implicitly_retry_on_config_stepdowns.js override
Root Cause: SERVER-108482 correctly removed the isNotPrimaryError retry from kNotIdempotent in Shard::remoteIsRetriableError, which had previously masked config-stepdown errors by silently retrying setDefaultRWConcern at the C++ layer before they reached the JS test layer. With that safety net gone, when the config primary steps down during write-concern satisfaction of setDefaultRWConcern, the response surfaces as writeConcernError: "code: 6, HostUnreachable, "operation was interrupted" ": an
SERVER-98874Closed
[v5.0] Fix flaky 5.0-specific test
The v5.0-only test file, introduced in SERVER-94839 is flaky. We need to fix it
SERVER-126021Closed
Undefined behavior when inserting data with duplicate field names into timeseries collections
{panel:title=Issue Status as of May 12th, 2026|borderColor=#cccccc|titleBGColor=#6cb33f|bgColor=#eeeeee} *SUMMARY* This is a critical fix to address [CVE-2026-8053|https://www.cve.org/CVERecord?id=CVE-2026-8053]. Upgrade to MongoDB 8.3.2, 8.2.9, 8.0.23, 7.0.34, 6.0.28, 5.0.33. *ISSUE DESCRIPTION AND IMPACT* An issue in MongoDB Server's time-series collection implementation allows an authenticated user with database write privileges to trigger an out-of-bounds memory write in the mong
SERVER-115508Closed
Make minimally sized buffers for uncompressed Messages
{panel:title=Issue Status as of Dec 29 2025|borderColor=#cccccc|titleBGColor=#6cb33f|bgColor=#eeeeee} *SUMMARY* This is a critical fix to address [CVE-2025-14847|https://www.cve.org/CVERecord?id=CVE-2025-14847]. Upgrade to 8.2.3, 8.0.17, 7.0.28, 6.0.27, 5.0.32, or 4.4.30. *ISSUE DESCRIPTION AND IMPACT* An client-side exploit of the Server's zlib implementation can return uninitialized heap memory without authenticating to the server. We strongly recommend upgrading to a fixed version