-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
When a retryable write fails with error code 20 and an error message starting with "Transaction numbers" drivers must change the error message to:
"This MongoDB deployment does not support retryable writes. Please add retryWrites=false to your connection string."
Before raising the error back to the application. See this spec change for further details.
- depends on
-
PYTHON-2048 Raise an actionable error message when bulk_write/insert_many retryWrites fails due to using an unsupported storage engine or standalone
- Closed
-
CDRIVER-3270 Raise an actionable error message when retryWrites fails due to using an unsupported storage engine
- Closed
-
CSHARP-2678 Raise an actionable error message when retryWrites fails due to using an unsupported storage engine
- Closed
-
CXX-1806 Raise an actionable error message when retryWrites fails due to using an unsupported storage engine
- Closed
-
GODRIVER-1219 Raise an actionable error message when retryWrites fails due to using an unsupported storage engine
- Closed
-
JAVA-3374 Raise an actionable error message when retryWrites fails due to using an unsupported storage engine
- Closed
-
MOTOR-364 Raise an actionable error message when retryWrites fails due to using an unsupported storage engine
- Closed
-
NODE-2098 Raise an actionable error message when retryWrites fails due to using an unsupported storage engine
- Closed
-
PYTHON-1934 Raise an actionable error message when retryWrites fails due to using an unsupported storage engine
- Closed
-
RUBY-1896 Raise an actionable error message when retryWrites fails due to using an unsupported storage engine
- Closed
-
PHPC-1422 Raise an actionable error message when retryWrites fails due to using an unsupported storage engine
- Closed
-
RUST-416 Raise an actionable error message when retryWrites fails due to using an unsupported storage engine
- Closed
- is related to
-
SERVER-44591 Unhelpful error message about transactions in a sharded cluster with a standalone shard when trying to use retryable writes
- Open
- related to
-
SERVER-43889 Distinguish between a retryable write and a transaction when failing a command
- Closed