- 1.63.0 (latest)
- 1.62.0
- 1.61.0
- 1.59.0
- 1.58.0
- 1.57.0
- 1.56.0
- 1.55.0
- 1.54.0
- 1.53.0
- 1.52.0
- 1.51.0
- 1.50.0
- 1.49.0
- 1.47.0
- 1.46.0
- 1.45.0
- 1.44.0
- 1.43.0
- 1.42.0
- 1.41.0
- 1.40.0
- 1.39.0
- 1.38.0
- 1.37.0
- 1.34.0
- 1.33.0
- 1.32.0
- 1.31.0
- 1.30.0
- 1.29.0
- 1.28.0
- 1.27.0
- 1.26.0
- 1.25.0
- 1.24.0
- 1.23.0
- 1.22.0
- 1.21.0
- 1.20.0
- 1.19.0
- 1.18.0
- 1.17.0
- 1.16.0
- 1.15.0
- 1.14.0
- 1.13.0
- 1.12.1
- 1.11.0
- 1.9.1
- 1.8.1
- 1.7.2
- 1.6.0-beta
public enum HealthStatus.WeightError extends Enum<HealthStatus.WeightError> implements ProtocolMessageEnum
Protobuf enum google.cloud.compute.v1.HealthStatus.WeightError
Implements
ProtocolMessageEnumFields
Name | Description |
INVALID_WEIGHT | 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). |
INVALID_WEIGHT_VALUE | 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). |
MISSING_WEIGHT | The response to a Health Check probe did not have the HTTP response header field X-Load-Balancing-Endpoint-Weight. |
MISSING_WEIGHT_VALUE | The response to a Health Check probe did not have the HTTP response header field X-Load-Balancing-Endpoint-Weight. |
UNAVAILABLE_WEIGHT | 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. |
UNAVAILABLE_WEIGHT_VALUE | 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. |
UNDEFINED_WEIGHT_ERROR | A value indicating that the enum field is not set. |
UNDEFINED_WEIGHT_ERROR_VALUE | A value indicating that the enum field is not set. |
UNRECOGNIZED | |
WEIGHT_NONE | 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. |
WEIGHT_NONE_VALUE | 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. |
Methods
Name | Description |
forNumber(int value) | |
getDescriptor() | |
getDescriptorForType() | |
getNumber() | |
getValueDescriptor() | |
internalGetValueMap() | |
valueOf(Descriptors.EnumValueDescriptor desc) | |
valueOf(int value) | (deprecated) Use #forNumber(int) instead. |
valueOf(String name) | |
values() |