Skip to content
Cyoda Documentation
Settings

TX_COORDINATOR_NOT_CONFIGURED — distributed transaction coordination not available

cyoda-go version 0.8.3

errors.TX_COORDINATOR_NOT_CONFIGURED

Section titled “errors.TX_COORDINATOR_NOT_CONFIGURED”

NAME

Section titled “NAME”

TX_COORDINATOR_NOT_CONFIGURED — a requested capability requires distributed transaction coordination that is not available on this node.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 503 Service Unavailable. Retryable: no.

DESCRIPTION

Section titled “DESCRIPTION”

Reserved. Not currently emitted by any cyoda-go code path.

cyoda-go does not run a distributed two-phase-commit coordinator. Transactions are request-scoped and owned by the node that began them. A signed tx-token ({NodeID, TxRef}) carries the owning node’s identity so that callbacks and subsequent requests in the same transaction are routed to the correct node without any external coordinator.

This error code is reserved for a future capability where distributed multi-transaction coordination may be required. If you receive it from a current cyoda-go release, it indicates an unexpected condition; raise a support ticket.

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 — Reserved. Not currently emitted by any cyoda-go code path.
  • cyoda help errors TX_NO_STATE — Reserved. Not currently emitted by any cyoda-go code path.

Raw formats

Section titled “Raw formats”