You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Either I'm not configuring it right or the balancer doesn't actually balance the load between the servers.
My setup is the following:
a two node service getting written to
3 nodes discovering the service via Consul and posting data to it
When I start the 3 consumers, they each latch onto one of the two service servers and never let go. In the case below, two consumers latch onto one node in the service while the third latches onto the second (which I guess is a bit better than all three on one but theoretically worse than a simple randomization strategy).
Consumer 1:
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.69.231:32778/sales-record
Calling out to: http://172.31.69.231:32778/sales-record
Calling out to: http://172.31.69.231:32778/sales-record
Calling out to: http://172.31.69.231:32778/sales-record
Calling out to: http://172.31.69.231:32778/sales-record
Calling out to: http://172.31.69.231:32778/sales-record
Calling out to: http://172.31.69.231:32778/sales-record
Consumer 2:
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.69.231:32778/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Consumer 3:
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.69.231:32778/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
Calling out to: http://172.31.65.172:32781/sales-record
The behavior is the same for the default balancer options as well. Since basic client-side load balancing was the goal of importing this project, this is a deal breaker for me.
The text was updated successfully, but these errors were encountered:
Either I'm not configuring it right or the balancer doesn't actually balance the load between the servers.
My setup is the following:
When I start the 3 consumers, they each latch onto one of the two service servers and never let go. In the case below, two consumers latch onto one node in the service while the third latches onto the second (which I guess is a bit better than all three on one but theoretically worse than a simple randomization strategy).
Consumer 1:
Consumer 2:
Consumer 3:
The configuration used is as follows:
The behavior is the same for the default balancer options as well. Since basic client-side load balancing was the goal of importing this project, this is a deal breaker for me.
The text was updated successfully, but these errors were encountered: