Reference documentation and code samples for the Compute V1 Client class WeightError.
Protobuf type google.cloud.compute.v1.HealthStatus.WeightError
Namespace
Google \ Cloud \ Compute \ V1 \ HealthStatusMethods
static::name
Parameter | |
---|---|
Name | Description |
value |
mixed
|
static::value
Parameter | |
---|---|
Name | Description |
name |
mixed
|
Constants
UNDEFINED_WEIGHT_ERROR
Value: 0
A value indicating that the enum field is not set.
Generated from protobuf enum UNDEFINED_WEIGHT_ERROR = 0;
INVALID_WEIGHT
Value: 383698400
The response to a Health Check probe had the HTTP response header field X-Load-Balancing-Endpoint-Weight, but its content was invalid (i.e., not a non-negative single-precision floating-point number in decimal string representation).
Generated from protobuf enum INVALID_WEIGHT = 383698400;
MISSING_WEIGHT
Value: 384027537
The response to a Health Check probe did not have the HTTP response header field X-Load-Balancing-Endpoint-Weight.
Generated from protobuf enum MISSING_WEIGHT = 384027537;
UNAVAILABLE_WEIGHT
Value: 439464295
This is the value when the accompanied health status is either TIMEOUT (i.e.,the Health Check probe was not able to get a response in time) or UNKNOWN. For the latter, it should be typically because there has not been sufficient time to parse and report the weight for a new backend (which is with 0.0.0.0 ip address). However, it can be also due to an outage case for which the health status is explicitly reset to UNKNOWN.
Generated from protobuf enum UNAVAILABLE_WEIGHT = 439464295;
WEIGHT_NONE
Value: 502428831
This is the default value when WeightReportMode is DISABLE, and is also the initial value when WeightReportMode has just updated to ENABLE or DRY_RUN and there has not been sufficient time to parse and report the backend weight.
Generated from protobuf enum WEIGHT_NONE = 502428831;