Fluxheim/Dokumenti/Profil tal-bilanċjar tat-tagħbija

Profil tal-bilanċjar tat-tagħbija

Run several upstreams behind one public endpoint. Start simple, then add health checks and runtime controls.

Żewġ upstreams

[[vhosts.routes]]
name = "app"
path_prefix = "/"
action = "proxy"

[vhosts.routes.proxy]
upstreams = [
  "10.0.0.11:8080",
  "10.0.0.12:8080",
]
upstream_weights = [100, 50]
upstream_aliases = ["app-a", "app-b"]

Kontrolli tal-bilanċjar

Kontroll	Użah meta
`upstream_weights`	Il-backends għandhom jirċievu ishma tat-traffiku differenti.
`backup_upstreams`	Some backends should be used biss when primary choices fail.
`drain_upstreams`	Backend għandu jtemm ix-xogħol eżistenti iżda ma jirċievi l-ebda traffiku ġdid.
`disabled_upstreams`	Backend għandu jinżamm barra mir-rotazzjoni.
`upstream_max_in_flight`	A backend needs a lokali concurrency cap.

Fajl upstream dinamiku

[vhosts.routes.proxy]
upstreams_file = "/run/fluxheim/backends/app.txt"
upstreams_file_refresh_secs = 5

Use static upstreams when you need weights, aliases, backup, drain, jew disabled state. File u DNS refreshed pools intentionally keep the contract smaller.

X’jagħtik

Focused load-balancer release images are available.
Health checks jistgħu jżommu backends miksura barra mir-rotazzjoni.
Operazzjonijiet drain u force-down jgħinu waqt twieqi ta’ manutenzjoni.
Ġestit-cookie affinity is available when sessions need a stabbli backend.