Passive health checks not behaving as expected.

[puneethps]

Is there an existing issue for this?

• [X] I have searched the existing issues

Kong version ($ kong version)

3.2.2

Current Behavior

When I enable passive health checks for an upstream even though the number of failures exceed the configured value the target is not marked as unhealthy and requests are proxied to it, in the logs we see unhealthy TIMEOUT increment (215/1).

We also see worker.lua:164: failed to store event: queue overflow

Expected Behavior

Expected behaviour is to mark the target as unhealthy and requests shouldn't be proxied to that instance

Steps To Reproduce

No response

Anything else?

No response