I'm looking at setting up a multi-site radosgw configuration where data is sharded over multiple clusters in a single physical location; and would like to understand how Ceph handles requests in this configuration. Looking through the radosgw source[1] it looks like radowgw will return 301 redirect if I request a bucket that is not in the current zonegroup. This redirect appears to be to the endpoint for the zonegroup (I assume as configured by `radosgw-admin zonegroup create --endpoints`). This seems like it would work well for multiple geographic regions (e.g. us-east and us-west) for ensuring that a request is redirected to the region (zonegroup) that hosts the bucket. We could possibly improve this by virtual hosted buckets and having DNS point to the correct region for that bucket. I notice that it's also possible to configure zones in a zonegroup that don't peform replication[2] (e.g. us-east-1 and us-east-2). In this case I assume that if I direct a request to the wrong zone, then Ceph will just report that the object as not-found because, despite the bucket metadata being replicated from the zonegroup master, the objects will never be replicated from one zone to the other. Another layer (like a consistent hash across the bucket name or database) would be required for routing to the correct zone. Is this mostly correct? Are there other ways of controlling which cluster data is placed (i.e. placement groups)? Thanks! 1. https://github.com/ceph/ceph/blob/affb7d396f76273e885cfdbcd363c1882496726c/src/rgw/rgw_op.cc#L653-L669 2. https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/2/html/object_gateway_guide_for_red_hat_enterprise_linux/multi_site#configuring_multiple_zones_without_replication -- David Coles _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |