All Downloads are FREE. Search and download functionalities are using the official Maven repository.

target.apidocs.com.google.api.services.compute.model.HttpRetryPolicy.html Maven / Gradle / Ivy







HttpRetryPolicy (Compute Engine API v1-rev20200104-1.30.8)












com.google.api.services.compute.model

Class HttpRetryPolicy

    • Constructor Detail

      • HttpRetryPolicy

        public HttpRetryPolicy()
    • Method Detail

      • getNumRetries

        public Long getNumRetries()
        Specifies the allowed number retries. This number must be > 0. If not specified, defaults to 1.
        Returns:
        value or null for none
      • setNumRetries

        public HttpRetryPolicy setNumRetries(Long numRetries)
        Specifies the allowed number retries. This number must be > 0. If not specified, defaults to 1.
        Parameters:
        numRetries - numRetries or null for none
      • getPerTryTimeout

        public Duration getPerTryTimeout()
        Specifies a non-zero timeout per retry attempt. If not specified, will use the timeout set in HttpRouteAction. If timeout in HttpRouteAction is not set, will use the largest timeout among all backend services associated with the route.
        Returns:
        value or null for none
      • setPerTryTimeout

        public HttpRetryPolicy setPerTryTimeout(Duration perTryTimeout)
        Specifies a non-zero timeout per retry attempt. If not specified, will use the timeout set in HttpRouteAction. If timeout in HttpRouteAction is not set, will use the largest timeout among all backend services associated with the route.
        Parameters:
        perTryTimeout - perTryTimeout or null for none
      • getRetryConditions

        public List<String> getRetryConditions()
        Specfies one or more conditions when this retry rule applies. Valid values are: - 5xx: Loadbalancer will attempt a retry if the backend service responds with any 5xx response code, or if the backend service does not respond at all, example: disconnects, reset, read timeout, connection failure, and refused streams. - gateway-error: Similar to 5xx, but only applies to response codes 502, 503 or 504. - - connect-failure: Loadbalancer will retry on failures connecting to backend services, for example due to connection timeouts. - retriable-4xx: Loadbalancer will retry for retriable 4xx response codes. Currently the only retriable error supported is 409. - refused-stream:Loadbalancer will retry if the backend service resets the stream with a REFUSED_STREAM error code. This reset type indicates that it is safe to retry. - cancelledLoadbalancer will retry if the gRPC status code in the response header is set to cancelled - deadline-exceeded: Loadbalancer will retry if the gRPC status code in the response header is set to deadline-exceeded - resource-exhausted: Loadbalancer will retry if the gRPC status code in the response header is set to resource-exhausted - unavailable: Loadbalancer will retry if the gRPC status code in the response header is set to unavailable
        Returns:
        value or null for none
      • setRetryConditions

        public HttpRetryPolicy setRetryConditions(List<String> retryConditions)
        Specfies one or more conditions when this retry rule applies. Valid values are: - 5xx: Loadbalancer will attempt a retry if the backend service responds with any 5xx response code, or if the backend service does not respond at all, example: disconnects, reset, read timeout, connection failure, and refused streams. - gateway-error: Similar to 5xx, but only applies to response codes 502, 503 or 504. - - connect-failure: Loadbalancer will retry on failures connecting to backend services, for example due to connection timeouts. - retriable-4xx: Loadbalancer will retry for retriable 4xx response codes. Currently the only retriable error supported is 409. - refused-stream:Loadbalancer will retry if the backend service resets the stream with a REFUSED_STREAM error code. This reset type indicates that it is safe to retry. - cancelledLoadbalancer will retry if the gRPC status code in the response header is set to cancelled - deadline-exceeded: Loadbalancer will retry if the gRPC status code in the response header is set to deadline-exceeded - resource-exhausted: Loadbalancer will retry if the gRPC status code in the response header is set to resource-exhausted - unavailable: Loadbalancer will retry if the gRPC status code in the response header is set to unavailable
        Parameters:
        retryConditions - retryConditions or null for none

Copyright © 2011–2020 Google. All rights reserved.





© 2015 - 2025 Weber Informatics LLC | Privacy Policy