yyyar / gobetween

:cloud: Modern & minimalistic load balancer for the Сloud era
http://gobetween.io
Other
1.91k stars 210 forks source link

load balance but dont stick #316

Closed jhallam3 closed 2 years ago

jhallam3 commented 3 years ago

Hi. how can I call a url call it localhost:6000 and then each time I call it it moves to a different host thats in the load balanced group?

jhallam3 commented 3 years ago

this is what I have

[logging] level = "debug"

output = "/logs/log.txt"

output = "stdout" format = "text"

[defaults] max_connections = 0 # Maximum simultaneous connections to the server client_idle_timeout = "0" # Client inactivity duration before forced connection drop backend_idle_timeout = "0" # Backend inactivity duration before forced connection drop backend_connection_timeout = "0" # Backend connection timeout (ignored in udp)

[servers.sample] protocol = "tcp" bind = "0.0.0.0:5555" balance = "iphash" backend_connection_timeout = "5s" [servers.sample.discovery] kind = "docker" interval = "10s" timeout = "2s" docker_endpoint = "http://localhost:2375" docker_container_private_port = 8081 docker_container_label = "proxied=true"

[servers.sample.healthcheck] fails = 1 passes = 1 interval = "60s" timeout = "1s" kind = "ping"

[servers.sample2] protocol = "tcp" bind = "0.0.0.0:3000" balance = "roundrobin" max_connections = 1 # Maximum simultaneous connections to the server

[servers.sample2.discovery] kind = "static" static_list = [ "localhost:22991 weight=40 priority=1", "localhost:22992 weight=40 priority=1", "localhost:22995 weight=40 priority=1" ]

illarion commented 2 years ago

@jhallam3 just use roundrobin balancing, it will give you new backend each time, unless your http client has no keep alive connections

jhallam3 commented 2 years ago

Great thanks

Sent from my iPhone

On 14 Oct 2021, at 14:37, Illarion Kovalchuk @.***> wrote:

 @jhallam3 just use roundrobin balancing, it will give you new backend each time, unless your http client has no keep alive connections

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.