Roman Khavronenko 07ad4f82cd app/vmauth: properly check for backend health before leastLoaded policy (#7489) ... Previously, vmauth could have pick `buMin` as least loaded backend without checking its status. In result, vmauth could have respond to the user with an error even if there were healthy backends. That could happen if healthy backends already had non-zero amount of concurrent requests executing at the moment of least-loaded backend choosing logic. Steps to reproduce: 1. Setup vmauth with two backends: healthy and non-healthy 2. Execute a bunch of concurrent requests against vmauth (i.e. Grafana dash reload) 3. Observe that some requests will fail with message that all backends are unavailable Addresses https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3061 --- Signed-off-by: hagen1778 <roman@victoriametrics.com> (cherry picked from commit a0a154511a)		2024-11-08 17:07:54 +01:00
..
_index.md	docs: move changelog to dir (#6853)	2024-08-22 16:59:17 +02:00
CHANGELOG.md	app/vmauth: properly check for backend health before leastLoaded policy (#7489)	2024-11-08 17:07:54 +01:00
CHANGELOG_2020.md	docs: spelling fixes (#7420)	2024-11-06 13:58:16 +01:00
CHANGELOG_2021.md	docs: spelling fixes (#7420)	2024-11-06 13:58:16 +01:00
CHANGELOG_2022.md	docs: spelling fixes (#7420)	2024-11-06 13:58:16 +01:00
CHANGELOG_2023.md	docs: spelling fixes (#7420)	2024-11-06 13:58:16 +01:00