-
Notifications
You must be signed in to change notification settings - Fork 705
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Multi-AZ Failover LoadBalancing #1212
base: main
Are you sure you want to change the base?
feat: Multi-AZ Failover LoadBalancing #1212
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A longer review will still be needed.
...c/main/java/org/springframework/cloud/loadbalancer/config/LoadBalancerAutoConfiguration.java
Outdated
Show resolved
Hide resolved
...c/main/java/org/springframework/cloud/loadbalancer/config/LoadBalancerAutoConfiguration.java
Outdated
Show resolved
Hide resolved
...c/main/java/org/springframework/cloud/loadbalancer/config/LoadBalancerAutoConfiguration.java
Outdated
Show resolved
Hide resolved
fb5a2fb
to
481305c
Compare
Any progress with this? @spencergibb |
No. Please be patient |
It's a big change. The earliest it would be merged would be when we start the 2023.0 release train (4.1.0 of spring cloud commons). We won't even start that until June. |
Thanks for your answer. I'll consider this, and if any corrections needed please feel free to mention me. |
…be added into cache
Updated feature: Instances will be added into a cache only when connection fails or 5xx error occurs. 4xx Errors will not be triggered. |
- assertNull -> assertThat.isNull
Hi, @spencergibb @OlgaMaciaszek Still needs to be reviewed? |
Hi @kworkbee, sorry, this feature didn't make it to the planned backlog for |
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