Closed cookandy closed 8 years ago
I can tell you how we are doing it.
If we have any DC problem we take it out from DNS traffic so this describe your situation 1.
btw. most problematic for mesos and marathon is zookeeper which is not a best solution for multiple DC.
Thanks @sielaq. Can you please tell me what the benefit is for running Consul across the WAN? For your DNS balancing between DC, is Consul doing that? I'd imagine you'd need a public DNS balancer (i.e. DynDNS) to handle the inbound requests to public IPs.
Do you use Consul WAN for anything?
Ad.1 The benefits of using consul across WAN are multiple:
a) your services can communicate with other DC in case a local one are unreachable
b) specify exactly which service from which DC should be used:
your_service.service.dc1.consul
For example: On an external PROXY (like Apache ProxyPass / Varnish / Nginx) you can specify from which DC you want to use the service.
c) another example little simple one :) you can specify which marathon should be used (from which DC)
marathon.service.dc1.consul
or marathon.service.dc2.consul
Ad.2 We are not using Consul for external DNS balancing, yes we have a public DNS that is agnostic from PaaS.
Ok, I understand now. Thanks for the information!
Hi,
I was wondering if anyone had any experience running PanteraS over multiple data centers? I know that Consul has support for multiple data centers, but what about Mesos?
How would you configure HA for this solution? I see two options:
I think in order to use the second option, Mesos would need to be configured as a cluster across the 2 data centers.
Does anyone have any experience with this type of configuration?