Eric Satterwhite

It happened again were a the synchronization was left in a bad state. We didn't change the configuration of anything directly. but some pods in our infrastructure that are associated...

#3207 sounds like the actual fix? The commit makes it sound like the fix is mainly to remove the error log. Does it prevent request from being sent to the...

@hanshuebner Thanks, this looks like it may be helpful but I'm not entirely sure the size of the configuration is entirely the problem. The problem seems to persist for long...

> This is an interesting point. Do you have the health checks enabled @esatterwhite ? I don't have those. The health checks are only configured on the pods themselves, Kong...

Although it feels unnecessary. between kubernetes + kong. This feels like a behavior that shouldn't happen let alone need to be configured explicitly

We also se this a lot when things restart ```txl ingress-kong-7fbc678578-4glkz kong-proxy 2022/06/22 15:30:03 [error] 1107#0: *6829049 [lua] balancers.lua:228: get_balancer(): balancer not found for test.default.80.svc, will create it, client: X.YYY.ZZ.11,...

> The issue that we've recently fixed caused Kong to stall when a new reconfiguration cycle was started while another one was active. > > [95d704e](https://github.com/Kong/kong/commit/95d704ee6095648e97c39a5d86ede8ec2b7f208b) [200f56e](https://github.com/Kong/kong/commit/200f56ee2e011e5c60420909a84d99ebf08f3059) [ef58cdd](https://github.com/Kong/kong/commit/ef58cdd37129c0b2ca7ec60e0fe19fbf581ef8ee) [de37b51](https://github.com/Kong/kong/commit/de37b510034108dc347bf62fa8adae9ca0748d2e) @hanshuebner...

If it is still reporting 503s what was the improvement?

For us it is pretty reproducible at scale. Restarting the kubernetes deployment w/ 300 pods will trigger many reconfigurations and IP changes to occur in close proximity. Several, if not...

I can confirm. The latency jump happens in DB-less mode as well