Mastering Spring Cloud

Fail on start and retry

Sometimes it doesn't make any sense to launch the application if the Config Server is unavailable. In this case, we would like to halt a client with an exception. To achieve this, we have to set the bootstrap configuration property spring.cloud.config.failFast to true. Such a radical solution is not always the desired behavior. If a Config Server is unreachable only occasionally, the better approach would be to keep trying to reconnect until it succeeds. The spring.cloud.config.failFast property still has to be equal to true, but we would also need to add the spring-retry library and spring-boot-starter-aop to the application classpath. The default behavior assumes to retry six times with an initial backoff interval ...