you're correct that the distinction is between metadata and data; metadata like users and buckets will replicate to all zonegroups, while object data only replicates within a single zonegroup. any given bucket is 'owned' by the zonegroup that creates it (or overridden by the LocationConstraint on creation). requests for data in that bucket sent to other zonegroups should redirect to the zonegroup where it resides the ability to create multiple zonegroups can be useful in cases where you want some isolation for the datasets, but a shared namespace of users and buckets. you may have several connected sites sharing storage, but only require a single backup for purposes of disaster recovery. there it could make sense to create several zonegroups with only two zones each to avoid replicating all objects to all zones in other cases, it could make more sense to isolate things in separate realms with a single zonegroup each. zonegroups just provide some flexibility to control the isolation of data and metadata separately On Thu, Jun 29, 2023 at 5:48 PM Yixin Jin <yjin77@xxxxxxxx> wrote: > > Hi folks, > In the multisite environment, we can get one realm that contains multiple zonegroups, each in turn can have multiple zones. However, the purpose of zonegroup isn't clear to me. It seems that when a user is created, its metadata is synced to all zones within the same realm, regardless whether they are in different zonegroups or not. The same happens to buckets. Therefore, what is the purpose of having zonegroups? Wouldn't it be easier to just have realm and zones? > Thanks,Yixin > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx > _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx