Skip to Content

Class MemcoUnavailableError

The service could not be reached, or was not ready to answer.

The one failure here a backoff is the right answer to: nothing about the request is wrong. The transport already replays it — three attempts in all — on MemoryOperations.listDomains, MemoryOperations.getMemory and the health probe, so seeing it from one of those means all three failed. Every other method is left alone, because replaying a write can record it twice, so retrying one of those is the caller's decision and carries that risk.

MemcoUnhealthyError extends this class, so an instanceof chain testing this one first never reaches it, and comparing name against 'MemcoUnavailableError' never matches it at all. Test for the unhealthy case explicitly, either way.

Hierarchy (View Summary)

Index
constructor
code codeName detail debugErrorString
code: Status

The gRPC status code, as @grpc/grpc-js's numeric status enum.

codeName: string

The status code's name, such as UNAUTHENTICATED.

detail: string

The service's own description of the failure, without the code prefix.

debugErrorString: string | undefined

gRPC's internal diagnostic string, when the call carried one.

Quickstart