@robinbraemer although having the check backend logic altered, which is much faster, it does create a couple problems that were fixed before:
- When the targeted backend is not reachable the console gets spammed with logs.
- Even though there is a second backend which is reachable, with your implementation it will always choose for the first backend, even though it will fail.
- It doesn't show the fallback in the ping, when every backend is not reachable.
Maybe there is a better way to handle. A semi way which instead of checking every time per backend, it uses a cache. Or we could use the connection that is created when the backend is checked, instead of ignoring it.
This better, but indeed slower, method could maybe be an extra option in the config, for users that have backends that frequently are not reachable.
Originally posted by @BorisP1234 in #538 (comment)
@robinbraemer although having the check backend logic altered, which is much faster, it does create a couple problems that were fixed before:
Maybe there is a better way to handle. A semi way which instead of checking every time per backend, it uses a cache. Or we could use the connection that is created when the backend is checked, instead of ignoring it.
This better, but indeed slower, method could maybe be an extra option in the config, for users that have backends that frequently are not reachable.
Originally posted by @BorisP1234 in #538 (comment)