Skip to content
Cyoda Documentation
Settings

SEARCH_SHARD_TIMEOUT — a search shard did not respond in time

cyoda-go version 0.6.2

errors.SEARCH_SHARD_TIMEOUT

Section titled “errors.SEARCH_SHARD_TIMEOUT”

NAME

Section titled “NAME”

SEARCH_SHARD_TIMEOUT — one or more search shards did not respond within the configured timeout, causing the search job to fail.

SYNOPSIS

Section titled “SYNOPSIS”

HTTP: 503 Service Unavailable. Retryable: yes.

DESCRIPTION

Section titled “DESCRIPTION”

Distributed search fans out to multiple shards in parallel. If any shard does not return results before the search timeout expires, the job is marked failed and this error is returned. Occurs under high load, during partial cluster degradation, or with expensive queries.

Retryable. Frequent timeouts indicate that the query scope, result limit, or cluster configuration requires adjustment.

SEE ALSO

Section titled “SEE ALSO”
  • errors
  • errors.SEARCH_JOB_NOT_FOUND
  • errors.DISPATCH_TIMEOUT

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 SEARCH_JOB_NOT_FOUND — Polling a search job by ID returns this error when the job ID is unknown or belongs to a different tenant. Jobs are tenant-scoped; a valid job ID from one tenant is not visible to another.
  • cyoda help errors DISPATCH_TIMEOUT — A workflow processor or criteria evaluation was dispatched to a compute member but the response did not arrive within the dispatch timeout window. The underlying task may or may not have completed on the remote node.

Raw formats

Section titled “Raw formats”