Skip to content
Cyoda Documentation
Settings

TRANSACTION_NODE_UNAVAILABLE — the node owning the transaction is unreachable

cyoda-go version 0.6.2

errors.TRANSACTION_NODE_UNAVAILABLE

Section titled “errors.TRANSACTION_NODE_UNAVAILABLE”

NAME

Section titled “NAME”

TRANSACTION_NODE_UNAVAILABLE — the cluster node that owns the open transaction is not alive or reachable.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 503 Service Unavailable. Retryable: yes.

DESCRIPTION

Section titled “DESCRIPTION”

Transaction state is pinned to the node that opened it. If that node crashes or becomes unreachable while the transaction is in progress, subsequent requests using the transaction token are rejected with this error because the proxy cannot forward them to the owner.

Retryable by opening a new transaction. The in-progress transaction is likely lost. Mid-transaction node failure requires the client to restart the transaction from scratch.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.TRANSACTION_EXPIRED
  • errors.TRANSACTION_NOT_FOUND
  • errors.CLUSTER_NODE_NOT_REGISTERED

See also

Section titled “See also”
  • cyoda help errors — Every error response from the Cyoda REST API carries a structured errorCode in the properties object. Multiple codes may share the same HTTP status. Programmatic handling keys on errorCode, not HTTP status.
  • cyoda help errors TRANSACTION_EXPIRED — Transaction tokens are short-lived bearer tokens issued when a transaction is opened. This error fires when the token’s exp claim is in the past at the time the proxy validates it. The transaction itself may still be active server-side, but the token is no longer valid for routing.
  • cyoda help errors TRANSACTION_NOT_FOUND — The transaction ID supplied in the request does not correspond to an active transaction. The transaction may have been committed, rolled back, expired, or may never have existed. Also occurs when a request is mis-routed to a node that never opened the transaction.
  • cyoda help errors CLUSTER_NODE_NOT_REGISTERED — The request was routed to or requires a specific cluster node that is not present in the registry. Occurs during startup, rolling restarts, or after a node failure before the gossip layer has converged.

Raw formats

Section titled “Raw formats”