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
I have 10 gateway instances (Ingress Gateway) and 10 "Proxy A" (Envoy) instances to which traffic from the gateway goes.
Than I have 2 "Proxy B" instances (Envoy also) that accept traffic from "Proxy A".
Load balancing from "Proxy A" to "Proxy B" working incorrect.
From the network load on the host, I can see that traffic is only going to one instance "Proxy B".
1st instance of Proxy B
2nd instance of Proxy B
If I redeployed nomad job "Proxy A" a workload balancing is going correctly.
1st instance of Proxy B
2nd instance of Proxy B
But when I redeployed the nomad job "Proxy B" the balancing "breaks down" again.
I tried writing the congfiguration to Consul for the "Proxy A"
Consul v1.14.7
Revision d97acc0a
Build Date 2023-05-16T01:36:41Z
The text was updated successfully, but these errors were encountered:
blake
changed the title
Service Mash is not balancing the workload evenly across multiple instances in Nomad cluster.
Service Mesh is not balancing the workload evenly across multiple instances in Nomad cluster.
Oct 3, 2024
Hi!
I have 10 gateway instances (Ingress Gateway) and 10 "Proxy A" (Envoy) instances to which traffic from the gateway goes.
Than I have 2 "Proxy B" instances (Envoy also) that accept traffic from "Proxy A".
Load balancing from "Proxy A" to "Proxy B" working incorrect.
From the network load on the host, I can see that traffic is only going to one instance "Proxy B".
1st instance of Proxy B
2nd instance of Proxy B
If I redeployed nomad job "Proxy A" a workload balancing is going correctly.
1st instance of Proxy B
2nd instance of Proxy B
But when I redeployed the nomad job "Proxy B" the balancing "breaks down" again.
I tried writing the congfiguration to Consul for the "Proxy A"
and for "Proxy B"
Envoy configuration file of "Proxy A"
Server nomad version
Server consul version
Client nomad version
Client consul version
The text was updated successfully, but these errors were encountered: