Class MemcoUnhealthyError
Hierarchy (View Summary)
- MemcoUnavailableError
- MemcoUnhealthyError
Constructors
constructor
-
new MemcoUnhealthyError(
code: Status,
detail: string,
debugErrorString?: string,
): MemcoUnhealthyErrorParameters
- code: Status
- detail: string
OptionaldebugErrorString: string
Returns MemcoUnhealthyError
Properties
Readonlycode
code: Status
The gRPC status code, as @grpc/grpc-js's numeric status enum.
ReadonlycodeName
codeName: string
The status code's name, such as UNAUTHENTICATED.
Readonlydetail
detail: string
The service's own description of the failure, without the code prefix.
ReadonlydebugErrorString
debugErrorString: string | undefined
gRPC's internal diagnostic string, when the call carried one.
The endpoint answered its health probe with something other than serving.
Raised only by the connection check, never by fromServiceError.
The endpoint and TLS are right — something answered — and the backend is not taking traffic. Nothing to reconfigure: wait, then call Memco.connect again. It leaves the channel open on failure, so a second attempt costs no fresh handshake. The credential is untested at this point, because the probe runs before the call that carries it.
A subclass of MemcoUnavailableError, so ordering matters when catching both: test for this one first.