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
{{ message }}
This repository has been archived by the owner on Dec 4, 2024. It is now read-only.
I'm researching container orchestration software for my thesis and used the marathon-lb for load-balancing. After three days of figuring out why the load balancer wouldn't work, I found out that using the option "port": 9999 instead of using "portIndex": 0 made it so that haproxy can't reach backend apps on another node. Haproxy could only reach backend apps if they were on the same node. Replacing the port option with the portindex option fixed this. I can't find how or why this would happen.
I don't require any more help, but I thought I'd leave this here for further references.
Hi everyone
I'm researching container orchestration software for my thesis and used the marathon-lb for load-balancing. After three days of figuring out why the load balancer wouldn't work, I found out that using the option "port": 9999 instead of using "portIndex": 0 made it so that haproxy can't reach backend apps on another node. Haproxy could only reach backend apps if they were on the same node. Replacing the port option with the portindex option fixed this. I can't find how or why this would happen.
I don't require any more help, but I thought I'd leave this here for further references.
App definition:
When
"portIndex": 0,
is replaced with"port":9999
, marathon-lb stops working.Marathon-lb definition
The text was updated successfully, but these errors were encountered: