The TemporarilyUnavailable error indicates that the operation has been aborted, likely due to excessive server load (e.g. transaction rolled back for eviction). This error is retried in the server with an increasingly larger backoff. Internal operations are retried indefinitely, user operations are retried up to a fixed number of attempts before returning TemporarilyUnavailable to the client.
------
Original title: Instead of WriteConflict, return a more specialized error when oldest transactions are rolled back for eviction
Original description: Currently, when a write operation is hitting the wt dirty threshold limit, we take the error from WiredTiger, a WT_ROLLBACK, and up-convert to a WriteConflict. This is misleading and should print something more specific instead. Something that would indicate the actual reason.
- backported by
-
SERVER-72910 [v5.0] Backport wtRCToStatus changes from SERVER-60839
-
- Closed
-
- depends on
-
WT-8290 Adding a new API to the session to return the rollback reason
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- is related to
-
SERVER-62650 RecordStore RecordId initialization can deadlock transactions with cache eviction
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Backlog
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Closed
-
- mentioned in
-
Page Loading...