Boy, Jewel is pretty old. Even Luminous is getting up there. There have been a lot of multisite improvements in Mimic and now Nautilus, so you might want to consider upgrading all the way to 14.2.4.
Anyway, the way we solve this is by giving each zone a different name (eg application1a/application1b), and then having a virtual IP for application1. We then move the virtual IP around whichever zone we want to have accepting traffic for that zonegroup. In our case we're advertising the virtual IP on all of the radosgw instances using bgp and then letting our routers do per-stream ECMP to load balance the traffic. Each RGW in each cluster checks the realm's period every few seconds and decides to announce/withdraw the IP based on whether that rgw's zone is the master zone for the zonegroup (plus whether the rgw instance is healthy, etc). We have both application1.example.com <http://application1.example.com/> and application1a/application1b.example.com <http://application1b.example.com/> as hostnames in the zonegroup config, but just application1.example.com <http://application1.example.com/> for the endpoint. I'm not sure what the equivalent settings are on Jewel's multisite, if any. If you're routing radosgw traffic through a reverse proxy or load balancer you can also rewrite the host header on the fly. Hope this helps, Ed > On Oct 9, 2019, at 10:02 AM, Melzer Pinto <melzer.pi...@mezocliq.com> wrote: > > Hello, > I have a question about multi site configuration. I have 2 clusters > configured in a single realm and zonegroup. One cluster is the master zone > and the other the slave. Lets assume the first cluster can be reached at > http://application1.something.com <http://application1.something.com/> and > the 2nd one is http://application1-slave.something.com > <http://application1-slave.something.com/>. My application has a number of > config files that reference http://application1.something.com > <http://application1.something.com/>. So if there is a site outage i'd need > to change all of these files to http://application1-slave.something.com > <http://application1-slave.something.com/> and restart. I was wondering if > there are any alternatives where I dont have to change the config files. The > best solution would be to use the same name in both clusters - > http://application1.something.com <http://application1.something.com/>. But > i'm not sure if that is recommended or doable even. Any suggestions? I'm > using the latest version of Ceph Jewel, 10.2.11, but I am planning to > upgrade to luminous soon. > > Thanks > M > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com <mailto:ceph-users@lists.ceph.com> > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > <http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com>
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
