Bug #20472
Updated by Peter Amstutz 12 months ago
I set the dispatcher ProbesPerSecond to 10 and it rapidly started to generate a request backlog on the API server. Seems like it is still fighting over the container table lock.
When I set it back to 5 per second, the backlog went away.
What the probes doing that causes it to slam the database like that?
Do container table updates need a separate limiter like the logs endpoint so they don't kill the API server?