minor fix #1342
minor fix #1342
Conversation
| Spring Cloud LoadBalancer creates a separate Spring child context for each service id. By default, these contexts are initialised lazily, whenever the first request for a service id is being load-balanced. | ||
|
|
||
| You can choose to load those contexts eagerly. In order to do that, specify the service ids for which you want to do eager load using the `spring.cloud-loadbalancer.eager-load.clients` property. | ||
| You can choose to load those contexts eagerly. In order to do that, specify the service ids for which you want to do eager load using the `spring.cloud-loadbalancer.eager-load.clients` property, for example: |
There was a problem hiding this comment.
I was writing some integration tests for spring-cloud-kubernetes (where I work most) and in one of them, I wanted to eager init load balancer. The documentation here was not clear enough for me that this property is actually an array of elements. imho, adding such a small example makes it clear.
|
while this might be a little beneficial, the only reason I wanted to do eager initialization, is because I don't know how to retrieve the In case you think this should be a separate question, just let me know... |
|
|
||
| Spring Cloud LoadBalancer creates a separate Spring child context for each service id. By default, these contexts are initialised lazily, whenever the first request for a service id is being load-balanced. | ||
|
|
||
| You can choose to load those contexts eagerly. In order to do that, specify the service ids for which you want to do eager load using the `spring.cloud-loadbalancer.eager-load.clients` property. |
There was a problem hiding this comment.
fixed a typo here, too:
spring.cloud-loadbalancer.eager-load.clients
vs
spring.cloud.loadbalancer.eager-load.clients
3 participants
No description provided.