diff --git a/multi/multi__spring_cloud_config_client.html b/multi/multi__spring_cloud_config_client.html index 9751cc19..0251b921 100644 --- a/multi/multi__spring_cloud_config_client.html +++ b/multi/multi__spring_cloud_config_client.html @@ -22,7 +22,7 @@ For example, the following YAML file is for a Config Server that is a Eureka cli configPath: /config

7.3 Config Client Fail Fast

In some cases, you may want to fail startup of a service if it cannot connect to the Config Server. If this is the desired behavior, set the bootstrap configuration property spring.cloud.config.fail-fast=true to make the client halt with an Exception.

7.4 Config Client Retry

If you expect that the config server may occasionally be unavailable when your application starts, you can make it keep trying after a failure. -First, you need to set spring.cloud.config.fail-fast=false. +First, you need to set spring.cloud.config.fail-fast=true. Then you need to add spring-retry and spring-boot-starter-aop to your classpath. The default behavior is to retry six times with an initial backoff interval of 1000ms and an exponential multiplier of 1.1 for subsequent backoffs. You can configure these properties (and others) by setting the spring.cloud.config.retry.* configuration properties.

[Tip]Tip

To take full control of the retry behavior, add a @Bean of type RetryOperationsInterceptor with an ID of configServerRetryInterceptor. diff --git a/single/spring-cloud-config.html b/single/spring-cloud-config.html index d7090cbc..fbf99f3c 100644 --- a/single/spring-cloud-config.html +++ b/single/spring-cloud-config.html @@ -654,7 +654,7 @@ For example, the following YAML file is for a Config Server that is a Eureka cli configPath: /config

7.3 Config Client Fail Fast

In some cases, you may want to fail startup of a service if it cannot connect to the Config Server. If this is the desired behavior, set the bootstrap configuration property spring.cloud.config.fail-fast=true to make the client halt with an Exception.

7.4 Config Client Retry

If you expect that the config server may occasionally be unavailable when your application starts, you can make it keep trying after a failure. -First, you need to set spring.cloud.config.fail-fast=false. +First, you need to set spring.cloud.config.fail-fast=true. Then you need to add spring-retry and spring-boot-starter-aop to your classpath. The default behavior is to retry six times with an initial backoff interval of 1000ms and an exponential multiplier of 1.1 for subsequent backoffs. You can configure these properties (and others) by setting the spring.cloud.config.retry.* configuration properties.

[Tip]Tip

To take full control of the retry behavior, add a @Bean of type RetryOperationsInterceptor with an ID of configServerRetryInterceptor. diff --git a/spring-cloud-config.xml b/spring-cloud-config.xml index 88e90c57..0128f9cd 100644 --- a/spring-cloud-config.xml +++ b/spring-cloud-config.xml @@ -1324,7 +1324,7 @@ If this is the desired behavior, set the bootstrap configuration property Config Client Retry If you expect that the config server may occasionally be unavailable when your application starts, you can make it keep trying after a failure. -First, you need to set spring.cloud.config.fail-fast=false. +First, you need to set spring.cloud.config.fail-fast=true. Then you need to add spring-retry and spring-boot-starter-aop to your classpath. The default behavior is to retry six times with an initial backoff interval of 1000ms and an exponential multiplier of 1.1 for subsequent backoffs. You can configure these properties (and others) by setting the spring.cloud.config.retry.* configuration properties.