From 6a8888afd15d19f54500311a1dcced15ba23c20c Mon Sep 17 00:00:00 2001 From: buildmaster Date: Thu, 30 Apr 2020 13:45:18 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- reference/html/index.html | 15 ++------------- reference/html/spring-cloud-commons.html | 15 ++------------- 2 files changed, 4 insertions(+), 26 deletions(-) diff --git a/reference/html/index.html b/reference/html/index.html index 102c1ecb..14ce0533 100644 --- a/reference/html/index.html +++ b/reference/html/index.html @@ -1585,22 +1585,11 @@ healthy instances after querying the external ServiceDiscovery.
-

The HealthCheckServiceInstanceListSupplier uses InstanceHealthChecker to verify if the instances are -alive. We provide a default PingHealthChecker instance. It uses WebClient to execute -requests against the health endpoint of the instance. You can also provide your own implementation -of InstanceHealthChecker instead.

-
-

HealthCheckServiceInstanceListSupplier uses properties prefixed with spring.cloud.loadbalancer.healthcheck. You can set the initialDelay and interval -for the scheduler.

-
-
-

For the PingHealthChecker, you can set the default path for the healthcheck URL by setting +for the scheduler. You can set the default path for the healthcheck URL by setting the value of the spring.cloud.loadbalancer.healthcheck.path.default. You can also set a specific value -for any given service by setting the value of the spring.cloud.loadbalancer.healthcheck.path.[SERVICE_ID], -substituting the [SERVICE_ID] with the correct ID of your service. If the path is not set, -/actuator/health is used by default.

+for any given service by setting the value of the spring.cloud.loadbalancer.healthcheck.path.[SERVICE_ID], substituting the [SERVICE_ID] with the correct ID of your service. If the path is not set, /actuator/health is used by default.

In order to use the health-check scheduler approach, you will have to instantiate a HealthCheckServiceInstanceListSupplier bean in a custom configuration.

diff --git a/reference/html/spring-cloud-commons.html b/reference/html/spring-cloud-commons.html index 102c1ecb..14ce0533 100644 --- a/reference/html/spring-cloud-commons.html +++ b/reference/html/spring-cloud-commons.html @@ -1585,22 +1585,11 @@ healthy instances after querying the external ServiceDiscovery.
-

The HealthCheckServiceInstanceListSupplier uses InstanceHealthChecker to verify if the instances are -alive. We provide a default PingHealthChecker instance. It uses WebClient to execute -requests against the health endpoint of the instance. You can also provide your own implementation -of InstanceHealthChecker instead.

-
-

HealthCheckServiceInstanceListSupplier uses properties prefixed with spring.cloud.loadbalancer.healthcheck. You can set the initialDelay and interval -for the scheduler.

-
-
-

For the PingHealthChecker, you can set the default path for the healthcheck URL by setting +for the scheduler. You can set the default path for the healthcheck URL by setting the value of the spring.cloud.loadbalancer.healthcheck.path.default. You can also set a specific value -for any given service by setting the value of the spring.cloud.loadbalancer.healthcheck.path.[SERVICE_ID], -substituting the [SERVICE_ID] with the correct ID of your service. If the path is not set, -/actuator/health is used by default.

+for any given service by setting the value of the spring.cloud.loadbalancer.healthcheck.path.[SERVICE_ID], substituting the [SERVICE_ID] with the correct ID of your service. If the path is not set, /actuator/health is used by default.

In order to use the health-check scheduler approach, you will have to instantiate a HealthCheckServiceInstanceListSupplier bean in a custom configuration.