-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Component/s: CSOT, Transactions
-
None
-
Needed
-
Summary
The transaction's convenient API spec currently says that, when applying exponential backoff between retries, if the delay would exceed CSOT's deadline, drivers are to raise the previously encountered error. Instead, drivers should raise a timeout error because CSOT has expired.
Motivation
Who is the affected end user?
N/A
How does this affect the end user?
N/A
How likely is it that this problem or use case will occur?
N/A
If the problem does occur, what are the consequences and how severe are they?
N/A
Is this issue urgent?
This is part of backpressure
Is this ticket required by a downstream team?
N/A
Is this ticket only for tests?
Does this ticket have any functional impact, or is it just test improvements?
Acceptance Criteria
- Clarify that if timeoutMS expires, a timeout error should be raised.
- split to
-
CXX-3414 Clarify expected error if backoff exceeds CSOT's deadline in withTransaction
-
- Backlog
-
-
RUST-2357 Clarify expected error if backoff exceeds CSOT's deadline in withTransaction
-
- Backlog
-
-
CDRIVER-6233 Clarify expected error if backoff exceeds CSOT's deadline in withTransaction
-
- Blocked
-
-
CSHARP-5869 Clarify expected error if backoff exceeds CSOT's deadline in withTransaction
-
- In Code Review
-
-
JAVA-6093 Clarify expected error if backoff exceeds CSOT's deadline in withTransaction
-
- In Code Review
-
-
RUBY-3770 Clarify expected error if backoff exceeds CSOT's deadline in withTransaction
-
- Ready for Work
-
-
GODRIVER-3810 Clarify expected error if backoff exceeds CSOT's deadline in withTransaction
-
- In Progress
-
-
PHPLIB-1783 Clarify expected error if backoff exceeds CSOT's deadline in withTransaction
-
- Closed
-
-
PYTHON-5716 Clarify expected error if backoff exceeds CSOT's deadline in withTransaction
-
- Closed
-
-
NODE-7430 Clarify expected error if backoff exceeds CSOT's deadline in withTransaction
-
- Needs Review
-