Skip to content
Cyoda Documentation
Settings

COMPUTE_MEMBER_DISCONNECTED — compute member dropped from the cluster

cyoda-go version 0.6.2

errors.COMPUTE_MEMBER_DISCONNECTED

Section titled “errors.COMPUTE_MEMBER_DISCONNECTED”

NAME

Section titled “NAME”

COMPUTE_MEMBER_DISCONNECTED — a compute member that was holding a workflow or processor assignment has disconnected.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 503 Service Unavailable. Retryable: yes.

DESCRIPTION

Section titled “DESCRIPTION”

The compute member responsible for executing a processor or workflow step disconnected before completing the operation. The task may or may not have been executed.

Retryable. The cluster re-routes to an available member. Callers must be idempotent or use an idempotency key when retrying. Persistent failures indicate insufficient compute capacity for the required tags.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.CLUSTER_NODE_NOT_REGISTERED
  • errors.NO_COMPUTE_MEMBER_FOR_TAG

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 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.
  • cyoda help errors NO_COMPUTE_MEMBER_FOR_TAG — Workflow processors are dispatched to nodes that advertise matching compute tags. When no node with the required tag is alive in the cluster within the configured wait timeout (CYODA_DISPATCH_WAIT_TIMEOUT), the operation is rejected with this error.

Raw formats

Section titled “Raw formats”