Driver retry policies
DataStax driver retry policies increase application error recovery and prevent unnecessary load.
Retry policies automatically allow DataStax drivers to retry requests upon encountering server errors such as read timeouts, write timeouts, and unavailable exceptions.
When the load balancing policy encounters a server error, it designates a node as a coordinator for the request. The coordinator routes the request to the replicas and returns the response to the driver.
Default driver retry policies
Each DataStax driver implements a default retry policy. Some drivers allow extended retry policies in addition to those already included to implement custom behavior.
The default retry policy retries a request when it is safe to do so while preserving the consistency level of the original request. Default retry policies are recommended for use in most deployments.
Driver-specific retry policies
Retry policies are defined within the drivers. Policies vary depending on the programming language and the specific driver implementation.
For driver-specific retry policies, see the appropriate documentation:
| Language | Retry Policies |
|---|---|
|
By default, retries are managed by the For more information about the Python driver retry policies, see the DataStax API documentation. |
|
For more information about the Node.js driver retry policies, see GitHub. |
|
For more information about the Java driver retry policies, see GitHub. |
|
For more information about the C++ driver retry policies, see GitHub. |
|
For general driver retry policy information, see the DataStax driver documentation. For more information about the default retry policy and other driver retry policies, see the DataStax API documentation. |
