Skip to content
Cyoda Documentation
Settings

CLUSTER_NODE_NOT_REGISTERED — target node is not in the cluster registry

cyoda-go version 0.6.2

errors.CLUSTER_NODE_NOT_REGISTERED

Section titled “errors.CLUSTER_NODE_NOT_REGISTERED”

NAME

Section titled “NAME”

CLUSTER_NODE_NOT_REGISTERED — the target cluster node has not registered itself with the gossip registry.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 503 Service Unavailable. Retryable: yes.

DESCRIPTION

Section titled “DESCRIPTION”

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.

Retryable. Gossip convergence determines when the node becomes available. Persistence beyond the expected convergence window indicates a node health or cluster membership issue.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.COMPUTE_MEMBER_DISCONNECTED

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 COMPUTE_MEMBER_DISCONNECTED — 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.

Raw formats

Section titled “Raw formats”