Metadata replication is about keeping a global namespace in all zones. It will replicate all of your users and bucket names, but not the data itself. That way you don't end up with a bucket named "mybucket" in your US and EU zones that are owned by different people. It's up to you to decide if this is something you want or not. Metadata replication won't protected against the primary zone going offline.
Data replication will copy the metadata and data. If the primary goes offline, you'll be able to read everything that has replicated to the secondary zone. You should make sure you have enough bandwidth between the zones (and that latency is low enough) to allow replication can keep up. If replication falls behind, anything not replicated will catch up when the primary comes back up. I haven't found any docs on the process to promote a secondary zone to primary. Right now, it doesn't look like a good idea. If the master goes offline, you can read from the secondary while you get the master back online. The failover/failback are expensive (time and bandwidth wise), so it would take a pretty big problem before it's a good idea to promote the secondary to primary. Regarding your FastCGI error, when I see that, it's because my RadosGW daemon isn't running. Check if it's running (`ps auxww | grep radosgw`). If it's not, try `start radosgw-all`, then restart apache. If that doesn't work, you might need some extra configs in ceph.conf. Wido den Hollander just posted some WSGI examples in a thread titled "REST API and uWSGI?" If you're still interested in getting WSGI to work, check th
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
