Skip to content
Cyoda Documentation
Settings

TX_COORDINATOR_NOT_CONFIGURED — distributed transaction coordinator is not enabled

cyoda-go version 0.6.2

errors.TX_COORDINATOR_NOT_CONFIGURED

Section titled “errors.TX_COORDINATOR_NOT_CONFIGURED”

NAME

Section titled “NAME”

TX_COORDINATOR_NOT_CONFIGURED — the request requires a distributed transaction coordinator but none is configured on this node.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 503 Service Unavailable. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Certain operations that span multiple storage shards require a distributed transaction coordinator. This error is returned when such an operation is attempted on a node where the coordinator component is disabled or misconfigured.

Not retryable on this node. Distributed transaction operations require the coordinator to be enabled via the relevant CYODA_TX_* environment variables, or must be routed to a node where the coordinator is enabled.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.TX_REQUIRED
  • errors.TX_NO_STATE

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 TX_REQUIRED — Certain write operations that require atomic multi-step coordination mandate a transaction context. Returned when such an operation is called without a transactionId header or query parameter.
  • cyoda help errors TX_NO_STATE — The two-phase commit coordinator tracks per-transaction state (prepared, committed, aborted). This error is returned when a commit or abort instruction references a transaction for which no state record exists, because the transaction was never prepared or was already cleaned up.

Raw formats

Section titled “Raw formats”