Toggle table of contents sidebar
errors – Exceptions raised by the pymongo package¶
Exceptions raised by PyMongo.
See also
This module is compatible with both the synchronous and asynchronous PyMongo APIs.
Raised when a connection to the database is lost and an attempt to auto-reconnect will be made.
In order to auto-reconnect you must handle this exception, recognizing that the operation which caused it has not necessarily succeeded. Future operations will attempt to open a new connection to the database (and will continue to raise this exception until the first successful connection is made).
Subclass of ConnectionFailure.
Exception class for bulk write errors.
Added in version 2.7.
results (_DocumentOut)
None
True if this error was caused by a timeout.
Added in version 4.2.
Exception class for client-level bulk write errors.
results (_DocumentOut)
verbose (bool)
None
A top-level error that occurred when attempting to communicate with the server or execute the bulk write.
This value may not be populated if the exception was thrown due to errors occurring on individual writes.
The results of any successful operations that were performed before the error was encountered.
Write concern errors that occurred during the bulk write.
This list may have multiple items if more than one server command was required to execute the bulk write.
Errors that occurred during the execution of individual write operations.
This list will contain at most one entry if the bulk write was ordered.
Raised when collection validation fails.
Raised when something is incorrectly configured.
Raised when a connection to the database cannot be made or is lost.
Raised while iterating query results if the cursor is invalidated on the server.
Added in version 2.7.
Raised when an encoded document is too large for the connected server.
Raised when an insert or update fails due to a duplicate key error.
Raised when creating a collection with encrypted_fields fails.
Added in version 4.4.
The encrypted_fields document that allows inferring which data keys are known to be created.
Note that the returned document is not guaranteed to contain information about all of the data keys that were created, for example in the case of an indefinite error like a timeout. Use the cause property to determine whether a definite or indefinite error caused this error, and only rely on the accuracy of the encrypted_fields if the error is definite.
Raised when encryption or decryption fails.
This error always wraps another exception which can be retrieved via the cause property.
Added in version 3.9.
cause (Exception)
None
The exception that caused this encryption or decryption error.
True if this error was caused by a timeout.
Added in version 4.2.
Raised when a database operation times out, exceeding the $maxTimeMS set in the query or command option.
Note
Requires server version >= 2.6.0
Added in version 2.7.
None
True if this error was caused by a timeout.
Added in version 4.2.
Raised when an invalid name is used.
Raised when a client attempts to perform an invalid operation.
Raised when trying to parse an invalid mongodb URI.
An operation on an open connection exceeded socketTimeoutMS.
The remaining connections in the pool stay open. In the case of a write operation, you cannot know whether it succeeded or failed.
Subclass of AutoReconnect.
True if this error was caused by a timeout.
Added in version 4.2.
The server responded “not primary” or “node is recovering”.
These errors result from a query, write, or command. The operation failed because the client thought it was using the primary but the primary has stepped down, or the client thought it was using a healthy secondary but the secondary is stale and trying to recover.
The client launches a refresh operation on a background thread, to update its view of the server as soon as possible after throwing this exception.
Subclass of AutoReconnect.
Added in version 3.12.
Raised when a database operation fails.
Added in version 2.7: The details attribute.
None
The error code returned by the server, if any.
The complete error document returned by the server.
Depending on the error that occurred, the error document may include useful information beyond just the error message. When connected to a mongos the error document may contain one or more subdocuments if errors occurred on multiple shards.
True if this error was caused by a timeout.
Added in version 4.2.
Raised for failures related to the wire protocol.
Base class for all PyMongo exceptions.
Return True if this error contains the given label.
Added in version 3.7.
True if this error was caused by a timeout.
Added in version 4.2.
Thrown when no MongoDB server is available for an operation
If there is no suitable server for an operation PyMongo tries for serverSelectionTimeoutMS (default 30 seconds) to find one, then throws this exception. For example, it is thrown after attempting an operation when PyMongo cannot connect to any server, or if you attempt an insert into a replica set that has no primary and does not elect one within the timeout window, or if you attempt to query with a Read Preference that the replica set cannot satisfy.
True if this error was caused by a timeout.
Added in version 4.2.
Raised when a database operation times out (i.e. wtimeout expires) before replication completes.
With newer versions of MongoDB the details attribute may include write concern fields like ‘n’, ‘updatedExisting’, or ‘writtenTo’.
Added in version 2.7.
None
True if this error was caused by a timeout.
Added in version 4.2.
Raised when an operation times out waiting to checkout a connection from the pool.
Subclass of ConnectionFailure.
Added in version 4.2.
True if this error was caused by a timeout.
Added in version 4.2.
Base exception type for errors raised due to write concern.
Added in version 3.0.
Base exception type for errors raised during write operations.
Added in version 3.0.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4