From e83ed57160e8a55354bad1cb3fc807f455b67773 Mon Sep 17 00:00:00 2001 From: buildmaster Date: Mon, 26 Nov 2018 14:51:57 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- multi/multi__spring_cloud_config_client.html | 2 +- single/spring-cloud-config.html | 2 +- spring-cloud-config.xml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/multi/multi__spring_cloud_config_client.html b/multi/multi__spring_cloud_config_client.html index 0251b921..9751cc19 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=true. +First, you need to set spring.cloud.config.fail-fast=false. 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 7dfef2ad..24435e61 100644 --- a/single/spring-cloud-config.html +++ b/single/spring-cloud-config.html @@ -600,7 +600,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=true. +First, you need to set spring.cloud.config.fail-fast=false. 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 ba460664..02b240ea 100644 --- a/spring-cloud-config.xml +++ b/spring-cloud-config.xml @@ -1239,7 +1239,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=true. +First, you need to set spring.cloud.config.fail-fast=false. 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.