feat: Multi-AZ Failover LoadBalancing #1212
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In a multi-AZ environment, a loadbalancer looks at
ServiceInstance
s of the primary zone first, but when the instances of that are not connected correctly, then it looks at the instances of the secondary zones.What's changed
spring.cloud.loadbalancer.configurations: multi-az-failover
: It enablesMultiAZFailoverServiceInstanceListSupplier
.spring.cloud.loadbalancer.secondary-zones: A,B,C
: Secondary Zones.To use this feature, Caching must be needed to record
ServiceInstances
into a cache for remembering connection-failed instances.MultiAZFailoverServiceInstanceListSupplier
will calculate available instances by comparing those in cache.Issues
Related to #1203