> This page location: /docs.md > /docs/development.md > /docs/manual/crud.md > /docs/manual/tutorial/query-documents.md

> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

# Retryable Reads

Retryable reads allow MongoDB drivers to automatically retry certain read operations a single time if they encounter certain network or server errors.

## Prerequisites

Minimum Driver Version

Official MongoDB drivers compatible with MongoDB Server 6.0 and later support retryable reads.

For more information on official MongoDB drivers, see [MongoDB Drivers.](https://www.mongodb.com/docs/drivers/)

Minimum Server Version

Drivers can only retry read operations if connected to MongoDB Server 6.0 or later.

## Enabling Retryable Reads

Official MongoDB drivers compatible with MongoDB Server 6.0 and later enable retryable reads by default. To explicitly disable retryable reads, specify [`retryReads=false`](https://www.mongodb.com/docs/manual/reference/connection-string-options.md#mongodb-urioption-urioption.retryReads) in the [connection string](https://www.mongodb.com/docs/manual/reference/connection-string.md#std-label-mongodb-uri) for the deployment.

[`mongosh`](https://www.mongodb.com/docs/mongodb-shell.md#mongodb-binary-bin.mongosh) does not support retryable reads.

## Retryable Read Operations

MongoDB drivers support retrying the following read operations. The list references a generic description of each method. For specific syntax and usage, defer to the driver documentation for that method.

| Methods | Descriptions |
| --- | --- |
| `Collection.aggregate``Collection.count``Collection.countDocuments``Collection.distinct``Collection.estimatedDocumentCount``Collection.find``Database.aggregate` For `Collection.aggregate` and `Database.aggregate`, drivers can only retry aggregation pipelines which do **not** include write stages, such as [`$out`](https://www.mongodb.com/docs/manual/reference/operator/aggregation/out.md#mongodb-pipeline-pipe.-out) or [`$merge`.](https://www.mongodb.com/docs/manual/reference/operator/aggregation/merge.md#mongodb-pipeline-pipe.-merge) | CRUD API Read Operations |
| `Collection.watch``Database.watch``MongoClient.watch` | Change Stream Operations |
| `MongoClient.listDatabases``Database.listCollections``Collection.listIndexes` | Enumeration Operations |
| GridFS Operations backed by `Collection.find` (e.g. `GridFSBucket.openDownloadStream`) | GridFS File Download Operations |

MongoDB drivers *may* include retryable support for other operations, such as helper methods or methods that wrap a retryable read operation. Defer to the [driver documentation](https://www.mongodb.com/docs/drivers/) to determine whether a method explicitly supports retryable reads.

**See also:**

Retryable Read Specification: [Supported Read Operations](https://github.com/mongodb/specifications/blob/master/source/retryable-reads/retryable-reads.rst#supported-read-operations)

### Unsupported Read Operations

The following operations do *not* support retryable reads:

- [`db.collection.mapReduce()`](https://www.mongodb.com/docs/manual/reference/method/db.collection.mapreduce.md#mongodb-method-db.collection.mapReduce)

- [`getMore`](https://www.mongodb.com/docs/manual/reference/command/getmore.md#mongodb-dbcommand-dbcmd.getMore)

- Any read command passed to a generic `Database.runCommand` helper, which is agnostic about read or write commands.

## Behavior

### Persistent Network Errors

MongoDB retryable reads make only **one** retry attempt. This helps address transient network errors or [replica set elections](https://www.mongodb.com/docs/manual/core/replica-set-elections.md#std-label-replica-set-elections), but not persistent network errors.

### Failover Period

The driver performs [server selection](https://www.mongodb.com/docs/manual/core/read-preference-mechanics.md#std-label-replica-set-read-preference-behavior) using the read command's original [read preference](https://www.mongodb.com/docs/manual/core/read-preference.md#std-label-read-preference) before retrying the read operation. If the driver cannot select a server for the retry attempt using the original read preference, the driver returns the original error.

The drivers wait [`serverSelectionTimeoutMS`](https://www.mongodb.com/docs/manual/reference/connection-string-options.md#mongodb-urioption-urioption.serverSelectionTimeoutMS) milliseconds before performing server selection. Retryable reads do not address instances where no eligible servers exist after waiting [`serverSelectionTimeoutMS`.](https://www.mongodb.com/docs/manual/reference/connection-string-options.md#mongodb-urioption-urioption.serverSelectionTimeoutMS)
