diff --git a/2.2.x/reference/html/appendix.html b/2.2.x/reference/html/appendix.html index e55c850c..288d1d67 100644 --- a/2.2.x/reference/html/appendix.html +++ b/2.2.x/reference/html/appendix.html @@ -276,7 +276,7 @@ Also, you can define your own properties.

spring.cloud.loadbalancer.cache.ttl

-

30s

+

35s

Time To Live - time counted from writing of the record, after which cache entries are expired, expressed as a {@link Duration}. The property {@link String} has to be in keeping with the appropriate syntax as specified in Spring Boot <code>StringToDurationConverter</code>. @see <a href= "https://github.com/spring-projects/spring-boot/blob/master/spring-boot-project/spring-boot/src/main/java/org/springframework/boot/convert/StringToDurationConverter.java">StringToDurationConverter.java</a>

@@ -286,7 +286,7 @@ Also, you can define your own properties.

spring.cloud.loadbalancer.health-check.interval

-

30s

+

25s

Interval for rerunning the HealthCheck scheduler.

diff --git a/2.2.x/reference/html/index.html b/2.2.x/reference/html/index.html index 7bb83132..c61a5f7e 100644 --- a/2.2.x/reference/html/index.html +++ b/2.2.x/reference/html/index.html @@ -1499,7 +1499,7 @@ as the value of the spring.cloud.loadbalancer.cache.ttl property. You can also set your own LoadBalancer cache initial capacity by setting the value of the spring.cloud.loadbalancer.cache.capacity property.

-

The default setup includes ttl set to 30 seconds and the default initialCapacity is 256.

+

The default setup includes ttl set to 35 seconds and the default initialCapacity is 256.

You can also altogether disable loadBalancer caching by setting the value of spring.cloud.loadbalancer.cache.enabled @@ -1631,7 +1631,7 @@ We suggest passing a DiscoveryClientServiceInstanceListSupplier del

You could use this sample configuration to set it up:

-
+
public class CustomLoadBalancerConfiguration {
 
@@ -1641,7 +1641,6 @@ We suggest passing a DiscoveryClientServiceInstanceListSupplier del
         return ServiceInstanceListSupplier.builder()
                     .withDiscoveryClient()
                     .withHealthChecks()
-                    .withCaching()
                     .build(context);
         }
     }
@@ -1649,6 +1648,10 @@ We suggest passing a DiscoveryClientServiceInstanceListSupplier del
+
NOTE
+
+

HealthCheckServiceInstanceListSupplier has its own caching mechanism based on Reactor Flux replay(), therefore, if it’s being used, you may want to skip wrapping that supplier with CachingServiceInstanceListSupplier.

+
TIP

In order to make working on your own LoadBalancer configuration easier, we have added a builder() method to the ServiceInstanceListSupplier class.

diff --git a/2.2.x/reference/html/spring-cloud-commons.html b/2.2.x/reference/html/spring-cloud-commons.html index 7bb83132..c61a5f7e 100644 --- a/2.2.x/reference/html/spring-cloud-commons.html +++ b/2.2.x/reference/html/spring-cloud-commons.html @@ -1499,7 +1499,7 @@ as the value of the spring.cloud.loadbalancer.cache.ttl property. You can also set your own LoadBalancer cache initial capacity by setting the value of the spring.cloud.loadbalancer.cache.capacity property.

-

The default setup includes ttl set to 30 seconds and the default initialCapacity is 256.

+

The default setup includes ttl set to 35 seconds and the default initialCapacity is 256.

You can also altogether disable loadBalancer caching by setting the value of spring.cloud.loadbalancer.cache.enabled @@ -1631,7 +1631,7 @@ We suggest passing a DiscoveryClientServiceInstanceListSupplier del

You could use this sample configuration to set it up:

-
+
public class CustomLoadBalancerConfiguration {
 
@@ -1641,7 +1641,6 @@ We suggest passing a DiscoveryClientServiceInstanceListSupplier del
         return ServiceInstanceListSupplier.builder()
                     .withDiscoveryClient()
                     .withHealthChecks()
-                    .withCaching()
                     .build(context);
         }
     }
@@ -1649,6 +1648,10 @@ We suggest passing a DiscoveryClientServiceInstanceListSupplier del
+
NOTE
+
+

HealthCheckServiceInstanceListSupplier has its own caching mechanism based on Reactor Flux replay(), therefore, if it’s being used, you may want to skip wrapping that supplier with CachingServiceInstanceListSupplier.

+
TIP

In order to make working on your own LoadBalancer configuration easier, we have added a builder() method to the ServiceInstanceListSupplier class.