Cross-datacenter service failover using Consul

[P Y]

Hello,
I'm working on evaluating Consul for the purpose of datacenter-aware DNS/service-discovery. Using "consul-vagrant", I have a 2-datacenter WAN cluster (dc1 and dc2), each consisting of 1 server and 2 clients, and a service ("somesvc.service.consul") running in both DCs.

My question is...if all "somesvc.service.consul" services go down in dc1 (dig returns no results in dc1), is it possible to have a query from within dc1 resolve to the address of "somesvc.service.consul" in dc2, or "somesvc.service.dc2.consul"? What I'm trying to achieve is for a client of this service to prefer the local DC's instance, but fall back to using the remote DC instance in the event there are no servers remaining in the local DC to service the request. One thing I did try was setting the "recursor" configuration value in each of the server nodes to be the opposite DC's server node, but that did not seem to work. Is this possible with Consul?

Thanks in advance for any assistance.

[Armon Dadgar]

Hey,

Take a look at this ticket: https://github.com/hashicorp/consul/issues/208

It is not currently possible to support this, but I think with a few special “meta” data centers,

this will become possible.

Best Regards,

Armon Dadgar

--
You received this message because you are subscribed to the Google Groups "Consul" group.
To unsubscribe from this group and stop receiving emails from it, send an email to consul-tool...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.