As a sidenote, I wouldn't recommend running marathon-lb on every node in the cluster. Running it on 3-5 should be sufficient for HA. You can simply round-robin (with DNS) between the marathon-lb instances (using, say, Mesos-DNS). The additional round trip delay you save by running marathon-lb on each machine is likely inconsequential.
On Thu, Mar 3, 2016 at 8:13 AM, Alfredo Carneiro < [email protected]> wrote: > Craig, soon I can increase my cluster and I will let you know okay? For > now, it is in production like a test!hehe > > On Thu, Mar 3, 2016 at 1:06 PM, craig w <[email protected]> wrote: > >> Alfredo -- i'll be curious to hear how it goes if you scale it up. I had >> initially tested with 12 nodes and it seemed fine, then when i went to 90 >> it became an issue. Again, this was with an older Marathon, so things could >> be much better now. >> >> On Thu, Mar 3, 2016 at 11:02 AM, Alfredo Carneiro < >> [email protected]> wrote: >> >>> I've just started to use it on production with 14 nodes and it is >>> scaling well! I had no problems yet. And different from >>> haproxy-marathon-bridge, it supports natively a loop every second, so you >>> don't have any delay, at least I haven't seen. >>> >>> On Thu, Mar 3, 2016 at 12:23 PM, craig w <[email protected]> wrote: >>> >>>> That was using the marathon-haproxy-bridge script, so it was polling >>>> marathon every minute to try and keep up to date. Though a minute lag in >>>> updating the proxy wasn't sufficient. >>>> >>> >>> >>> >>> -- >>> Alfredo Miranda >>> >> >> >> >> -- >> >> https://github.com/mindscratch >> https://www.google.com/+CraigWickesser >> https://twitter.com/mind_scratch >> https://twitter.com/craig_links >> >> > > > -- > Alfredo Miranda >
