Skip to content
Cyoda Documentation
Settings

COMPUTE_MEMBER_DISCONNECTED — compute member dropped from the cluster

cyoda-go version 0.8.4

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.

The server also raises this code when it evicts a member itself — after CYODA_KEEPALIVE_TIMEOUT seconds of inbound silence, or when one write to the member has stalled that long — and every callout in flight on that member fails with this code. It is also returned when a member leaves in the instant between being chosen for a callout and the request being handed to it: the caller gets this code immediately rather than waiting out errors.DISPATCH_TIMEOUT.

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
  • errors.DISPATCH_TIMEOUT
  • grpc

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.
  • cyoda help errors DISPATCH_TIMEOUT — A workflow processor, criteria evaluation, or function callout was dispatched to a compute member but the response did not arrive within the callout’s own responseTimeoutMs (a field on the processor, criteria, or function config; default 30000 ms) — not any cluster forwarding timeout.
  • cyoda help grpc — cyoda-go exposes one gRPC service: CloudEventsService (package org.cyoda.cloud.api.grpc). All gRPC methods use the CloudEvents Protobuf envelope (io.cloudevents.v1.CloudEvent) as both request and response types. The event type string in the CloudEvent envelope selects the operation; the JSON payload in text_data (or binary_data) carries the operation-specific body.

Raw formats

Section titled “Raw formats”