Staggering log volume when database is unavailable
We had service on a database the other day, and Zitadel is very enthusiastic about reporting errors, either DNS lookup failure or connection errors.
Here I reproduced the behaviour with a 4.1.3 install running in Docker Compose, and I stopped the
We're seeing about 1mio log-lines per minute, which I think is risky behaviour for stability. Would it at all be possible to add some throttling to the connection retry mechanism? It seems like it might be a bit too eager, at least to me.
Here I reproduced the behaviour with a 4.1.3 install running in Docker Compose, and I stopped the
dbdb instance, so DNS resolution would fail. These logs are from the Zitadel container:We're seeing about 1mio log-lines per minute, which I think is risky behaviour for stability. Would it at all be possible to add some throttling to the connection retry mechanism? It seems like it might be a bit too eager, at least to me.
