11601 Interrupted: Operation was interrupted
MongoDBWhat does it mean?
The running operation was interrupted. MongoDB terminated it before completion because of external intervention or a change in server state.
Why does it happen?
An administrator/tool killing the operation with db.killOp(); the server entering shutdown; a primary change in the replica set (stepdown/failover). (Exceeding maxTimeMS returns 50 MaxTimeMSExpired, not this error.) Long-running queries can be stopped this way.
How to fix it
Investigate why the operation was interrupted: currentOp/killOp history, failover events, server maintenance. If the operation is idempotent, retry it safely. Optimize and shorten long queries; add appropriate indexes. Use transient-error retry logic in the driver; ensure automatic reconnection on replica set failovers.
More from this engine
- 263 OperationNotSupportedInTransactionOperation not supported inside a multi-document transaction
- 20 IllegalOperationIllegal operation
- 48 NamespaceExistsNamespace (collection) already exists
- 85 IndexOptionsConflictIndex already exists with different options / different name
- 67 CannotCreateIndexCannot create index
- 27 IndexNotFoundIndex not found
- 79 UnknownReplWriteConcernUnknown replica set write concern